Intercom User and Company Sync
Keep Intercom profiles, companies, and plan attributes matching what the app knows.
What it adds
A sync that pushes app users, their workspaces, and a defined attribute set into Intercom and keeps them current as things change.
What your agent is told to do
5
What your agent is told to do
5-
1
Define the attribute contract before anything else: which fields the app owns and pushes, which fields support owns and the app must never touch, and which are read-only on both sides. Without that line drawn, the sync quietly erases the notes agents rely on.
-
2
Represent each workspace or organisation as a company and attach every user to the companies they genuinely belong to. A user in three workspaces is one profile with three associations, not three profiles.
-
3
Key on the app's internal user identifier so a profile survives an email change, and store the provider's identifier back on the app record so later updates target the right profile instead of guessing.
-
4
Run the initial backfill as a paced background job that honours the provider's rate limits and resumes from where it stopped. Ongoing updates should be incremental and fire only when a synced attribute actually changed.
-
5
Reuse the app's existing background-job system and credential storage. Do not call the provider from the browser or place the workspace token in client-side configuration, where it can be read and used against the account.
Edge cases it handles
8
Edge cases it handles
8- In a multi-workspace account a user must be associated only with the companies they belong to. A wrong association puts one customer's context in front of a conversation about another.
- Attributes that support staff maintain by hand must not be flattened by a stale app value. Push only app-owned fields, and only when they have changed.
- Profiles that were merged, deleted, or deactivated at the provider must be detected and reconciled. Writing blindly to a merged profile either fails or resurrects a record support deliberately cleaned up.
- A backfill will hit rate limits. Pace it, back off on the provider's own signal, and resume rather than restarting the whole run from the beginning.
- Removing a user from a workspace must remove the company association, not merely stop updating it. A stale association is a permanent leak that nobody notices.
- A user who deletes their account must be deleted or anonymised at the provider inside whatever window the app promises its users.
- Restricted content — card details, private message bodies, anything the support team has no business reading — must be excluded from synced attributes explicitly.
- When the provider is unreachable the app must keep working normally. Sync failures belong in a retry queue and an operator alert, never in a user's request path.
Definition of done
8
Definition of done
8- Every synced attribute has a documented owner and the sync writes only app-owned fields.
- Users are associated with exactly the companies they belong to, and removals propagate.
- Profiles are keyed on an internal identifier and the provider's identifier is stored back on the record.
- Backfills pace themselves against rate limits and resume after an interruption.
- Merged, deleted, and deactivated provider profiles are reconciled rather than blindly rewritten.
- Provider downtime never blocks, slows, or fails a user-facing request.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Mailgun Transactional Email
Mailgun Transactional Email
Send transactional email through Mailgun without losing bounce and complaint state.
What it does
A Mailgun delivery path bound to the correct region and sending domain, with durable suppression and event handling.
How it works
- 1 Put Mailgun behind the app's existing mail layer as one adapter. It is an alternative to the other transactional email integrations, not an addition; whichever adapter is in place, the template contract and suppression handling above it are unchanged.
- 2 Bind the region and sending domain in server-side configuration and validate at startup that they are consistent. A credential issued in one region will simply not work against another, and the failure looks like an authentication problem rather than a configuration one.
- 3 Check the suppression state for an address before a message is queued, not after the provider rejects it, so bouncing and complaining addresses stop consuming send attempts.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/mailgun-transactional-email
Firebase Cloud Messaging
Firebase Cloud Messaging
Deliver push through Firebase with registration tokens that stay valid as devices change.
What it does
A Firebase-backed push channel with server-side token lifecycle management, consistent payload handling across platforms, and safe handling of the routes a notification opens.
How it works
- 1 Store one record per device registration, tied to the account signed in at the time, the platform it came from, and when it was last confirmed working, and let one account hold many of them.
- 2 Send from the app's existing background-job system with the provider credentials held server-side, and treat every send as a job that can be retried rather than work done inline during a request.
- 3 Decide, per notification type, whether the payload is meant to be displayed by the platform or handled by the app, and keep that decision the same on every platform. The same event behaving as a visible alert on one platform and a silent update on another produces bugs nobody can reproduce.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/firebase-cloud-messaging
Slack Channel Alerts
Slack Channel Alerts
Send the events a team actually needs into a Slack channel without flooding it.
What it does
Operator-configured routing of selected app events into Slack channels, with grouping, throttling, and reliable delivery.
How it works
- 1 List the events genuinely worth interrupting a team for — failed payments, high-value signups, error thresholds, approvals waiting — and make each individually selectable per channel. An all-or-nothing firehose gets muted within a week and then nobody sees the one that mattered.
- 2 Run the connection through the provider's authorisation flow, then confirm the workspace and channel at setup by posting a test message the operator has to acknowledge. Store the resulting credential server-side only.
- 3 Write each message so it stands alone: what happened, to whom, when, and a link back into the app. Optional fields that are absent must be omitted cleanly rather than rendering as empty labels.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/slack-channel-alerts
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.