ActiveCampaign Contact Sync
Create or update ActiveCampaign contacts and place them in the right lists and automations.
What it adds
An outbound sync that upserts contacts, applies list membership and custom fields, and enrolls them in automations deliberately.
What your agent is told to do
5
What your agent is told to do
5-
1
Upsert every contact against one canonical identifier — the normalized email, or a stored provider contact ID once you have one — and never fall back to creating a record when a lookup times out.
-
2
Treat lists, tags, custom fields, and automation enrollment as four separate mappings with four separate rules. Collapsing them into one 'sync everything' action makes it impossible to change list membership without also re-firing an automation.
-
3
Enroll a contact in an automation only on the specific app event that warrants it, and record that the enrollment happened. A routine profile update must never re-enroll someone who is already in the sequence or has finished it.
-
4
If the app already has an outbound sync for another email provider, the connection storage, token refresh, backoff, and delivery-log machinery belong to that shared integration layer — extend it. This brief owns only the ActiveCampaign field, list, and automation mapping.
-
5
Do not drop rate-limited requests or retry them out of order. Queue per contact so that a create, an update, and a tag change for one person are applied in the sequence they occurred.
Edge cases it handles
8
Edge cases it handles
8- Two requests for the same person arriving close together will both fail their lookup and both create a contact. Serialize writes per canonical identifier so the second one finds what the first created.
- Lists, tags, custom fields, and automations behave differently on write: a list is membership, a tag is a marker, a custom field is data, and an enrollment is an action with side effects. Mapping them through one code path guarantees one of them is handled wrongly.
- An automation that restarts on every contact update will send the same welcome sequence repeatedly. Track prior enrollment and treat re-enrollment as an explicit, rare decision rather than the default.
- The provider reports contacts as unsubscribed or bounced, and that state outranks anything the app believes. Store it, stop sending, and show it on the contact record so support can explain why a customer is not receiving mail.
- Rate-limited requests that are retried independently will land out of order, applying a stale profile over a newer one. Preserve per-contact ordering through the retry, and back off on the whole queue rather than the individual call.
- Custom fields can be deleted or have their type changed after the mapping was saved. A write against a missing or mistyped field must pause the mapping with a message naming the field, not fail the whole sync silently.
- Access tokens expire and accounts get disconnected. Hold queued events, mark the connection broken in the app, and resume from the held queue once it is reconnected rather than discarding what accumulated.
- When the provider is unavailable, the app's own signup, purchase, or profile save must still complete. Show the sync as pending on the record instead of failing the user's action.
Definition of done
9
Definition of done
9- Concurrent events for one person produce a single contact, never a duplicate.
- List membership, tags, custom fields, and automation enrollment are configured and applied independently.
- A profile update never re-enrolls a contact in an automation they have already entered.
- Unsubscribed and bounced states reported by the provider stop further sends and are visible in the app.
- Rate limiting causes backoff and retry without reordering events for a contact.
- A deleted or retyped custom field pauses that mapping with a named, actionable error.
- The shared integration layer, not this feature, owns credentials, refresh, and delivery logs.
- 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.