Freshdesk Ticket Creation
Send support issues to Freshdesk with the context an agent needs to resolve them.
What it adds
A Freshdesk delivery path that maps in-app support requests onto the helpdesk's requester, group, product, and field structure.
What your agent is told to do
5
What your agent is told to do
5-
1
Build an operator-editable mapping from the app's request types onto requester, group, product, source, status, priority, and any custom fields. Field identifiers change whenever the helpdesk is reconfigured, so read them from configuration rather than embedding them in code.
-
2
Look up the contact by the session's address before creating one, and store the returned contact identifier on the app's user record so every later ticket reuses it instead of spawning a fresh contact each time.
-
3
Validate attachments against the provider's size and type limits in the browser and again on the server, and tell the user exactly what was rejected before the ticket is submitted.
-
4
Carry a request identifier generated before the first attempt and check for an existing ticket bearing it before creating one, so a timeout that actually succeeded does not file a duplicate.
-
5
If Zendesk or Help Scout briefs are also applied to this app, one shared submission path owns the form, context capture, attachments, and deduplication. This brief owns only the Freshdesk mapping and delivery.
Edge cases it handles
8
Edge cases it handles
8- Creating a new contact on every submission is the default failure mode here. Resolve and store the contact identifier, and reconcile it when the provider merges two contacts behind the app's back.
- A group, product, or custom field that has been renamed or removed must fail into an operator alert with the ticket still queued, rather than being dropped or filed into whatever queue happens to accept it.
- Files over the size limit or of a rejected type must be reported before submission, with the option to send the ticket without them rather than losing the whole request.
- A submission retried after a timeout must be deduplicated on the request identifier, because the first attempt may have already filed the ticket.
- Raw provider errors stay in the app's logs. The user sees a plain result and a reference they can quote, and agents do not receive the app's stack traces either.
- When the provider is unavailable the request must be accepted and queued with the user told it was received. Failing a help request when the user is already stuck is the worst possible moment to fail.
- Automatically attached context must exclude credentials, tokens, and full request bodies, which would otherwise be readable by every agent on the account.
- The ticket identifier must be stored against the app record so status can be shown and replies threaded correctly.
Definition of done
9
Definition of done
9- Request types map onto requester, group, product, source, status, and custom fields through configuration rather than code.
- Repeat submissions from the same user reuse a single provider contact.
- Attachment limits are enforced before submission and every rejection is explained to the user.
- A submission retried after a timeout yields exactly one ticket.
- Provider errors are logged internally while the user sees a plain outcome and a reference.
- Provider downtime queues the request instead of failing the submission.
- The ticket reference is stored against the app record.
- 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.