Constant Contact List Sync
Put new leads on the right Constant Contact list with their consent recorded.
What it adds
A background sync that creates or updates a Constant Contact contact and its list memberships whenever a lead is captured or its consent changes.
What your agent is told to do
5
What your agent is told to do
5-
1
Find every place the app captures an email address with marketing intent — signup, waitlist, lead form, checkout opt-in — and treat each as a sync source whose destination list an operator configures. Where an event-forwarding brief is also applied to this app, that one owns behavioural events; this one owns contact identity, consent, and list membership.
-
2
Match on the email address and update the existing contact rather than inserting a new one. Reuse the app's existing background-job system so the sync never runs inside the request that captured the lead.
-
3
Carry the consent evidence the app already holds — the wording shown, the timestamp, the capture source, the request context — and preserve the permission status on every write. A sync must never upgrade a contact to subscribed as a side effect.
-
4
Read the contact's current list memberships before writing, and send the union of those and the lists this sync intends to add. Do not send only the lists this feature owns: a full replacement silently strips memberships someone else added.
-
5
Hold the account credential server-side and refresh it ahead of expiry. Do not place the token in client-visible code and do not call the provider from the browser, where anyone can read it and anyone can forge a lead.
Edge cases it handles
7
Edge cases it handles
7- An address that already exists must update that contact rather than create a second one. Matching is case-insensitive and ignores surrounding whitespace.
- Permission-to-send status and the evidence behind it must survive every update. A contact who unsubscribed at the provider must not be resubscribed because the app still holds them as an active lead.
- A list deleted at the provider, or an account that has been disconnected, must fail the sync into a visible operator error with the affected leads retained, not drop them quietly.
- Reading memberships before writing them means two syncs racing on the same contact can each clobber the other. Serialise per contact so an update cannot remove a list added a moment earlier.
- A retried job must not trigger a second welcome message or automation series. Make each sync idempotent on the contact and apply only list changes that are genuinely new.
- Rate limits and provider outages need bounded backoff, and a lead that exhausts its attempts must land in a queue an operator can inspect and replay.
- An address the provider rejects as invalid or permanently bounced must be marked as such in the app rather than retried indefinitely.
Definition of done
9
Definition of done
9- Every marketing-intent capture point in the app syncs to an operator-configured list.
- Syncing an address that already exists updates that contact instead of creating a duplicate.
- Consent status and its evidence are preserved on every write, and no sync subscribes a contact who opted out.
- List memberships added outside the app survive an update from the app.
- A retried or duplicated job produces no second welcome message.
- A deleted list or disconnected account surfaces as an operator-visible error with the affected leads queued for replay.
- No provider credential is reachable from client-side code.
- 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.