Brevo Contact Sync
Add contacts to Brevo lists and keep their attributes and consent status current.
What it adds
A sync that upserts contacts into configured Brevo lists with correctly typed attributes and preserved consent state.
What your agent is told to do
5
What your agent is told to do
5-
1
Read the account's attribute definitions and their types when the mapping is configured, and validate each mapped app field against them, so a date, a number, and a text attribute are each sent in the form the account expects.
-
2
Treat list membership as additive by default. When updating a contact, send only the lists this sync is responsible for and leave every other membership alone rather than submitting a full replacement set.
-
3
Coalesce rapid changes to one contact into a single write using a short debounce keyed on the contact, so a burst of profile edits results in one update carrying the final state.
-
4
Read the contact's blocklist and unsubscribe status before writing, and skip any write that would re-enable sending. A new signup by a blocked address needs a fresh, recorded opt-in first.
-
5
Do not assume the account configuration you saw at setup still holds. Re-validate the destination lists and attributes before each run, and pause with a message naming what is missing rather than creating a replacement.
Edge cases it handles
8
Edge cases it handles
8- Attributes are typed, and a value sent in the wrong form is either rejected or silently coerced into something meaningless. Validate against the account's current attribute definitions rather than assuming everything is text.
- Blocked and unsubscribed contacts must never be re-enabled by a routine profile sync. Check the current state before writing, skip the write if it would resubscribe, and require a newly recorded opt-in to change that.
- A contact can belong to several lists, some of them managed by people outside the app. Submitting a complete list set on update silently removes the ones this sync does not know about, so only ever add or remove the lists it owns.
- Rapid profile changes generate a write per change and burn through the rate limit while applying states that are already stale. Debounce per contact and send the final state once.
- Lists get deleted and account configuration changes after the mapping was saved. Detect the missing destination, pause with a named error, and hold the queued contacts rather than sending them somewhere else.
- Job retries will resend the same update. Make writes idempotent on the contact's canonical email so a repeat is a no-op rather than a second list addition or a repeated welcome message.
- API credentials can be rotated or revoked at any time. Store them encrypted and server-side only, never in anything the browser receives, and mark the connection broken when they stop working.
- When the provider is down, the app's own signup or profile save must still complete and be confirmed. Queue the sync, show it as pending on the contact, and let an operator retry it.
Definition of done
9
Definition of done
9- Mapped attributes are validated against the account's current definitions and types before the mapping is saved.
- Blocked and unsubscribed contacts are never resubscribed without a newly recorded opt-in.
- Updates preserve list memberships this sync does not own.
- A burst of changes to one contact produces a single write carrying the final state.
- A deleted list or changed account configuration pauses the sync with a named error and holds queued work.
- Retried writes are idempotent and do not trigger repeated welcome messages.
- Credentials are stored encrypted server-side and never reach client-visible 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.