Salesforce Lead Creation
Push qualified leads into Salesforce with the fields and ownership sales needs to follow up.
What it adds
A push of qualified app leads into a configurable Salesforce object with mapped fields, ownership, and a visible sync status.
What your agent is told to do
5
What your agent is told to do
5-
1
Let an admin choose which object a lead becomes — a Lead, a Contact, or a custom object — because organizations model this differently and hardcoding one of them makes the feature unusable for half of them.
-
2
Read the target object's field definitions from the connected org at configuration time, including which fields are required and which picklist values are valid, and build the mapping from that rather than from assumptions.
-
3
Defer duplicate prevention to the org's configured matching and duplicate rules where they exist, and handle the resulting duplicate response as an expected outcome that links to the existing record, not as an error.
-
4
Set an owner using a rule the admin configures — a named user, a queue, or round-robin over a group — and fall back to a defined default when the mapped owner is inactive. An unowned lead is a lead nobody follows up.
-
5
Do not surface raw provider errors to end users. Log the full detail for operators, and show the person who submitted the form a plain confirmation that their submission was received.
Edge cases it handles
8
Edge cases it handles
8- Organizations use Leads, Contacts, and custom objects in incompatible ways, and some do not use Leads at all. The target object and its field mapping must be configuration, or the integration only fits the org it was written against.
- Required fields and picklists vary by org and by record type, and an unknown picklist value is rejected outright. Read the schema from the connected org and validate the mapping against it before saving, not on the first live lead.
- Creating without consulting the org's matching rules floods the pipeline with duplicates. When the org reports a duplicate, treat that as success, link the app record to the existing one, and record why no new record was created.
- Sessions expire and orgs enforce hard API request limits that the app can exhaust in a backfill. Refresh proactively, back off and requeue on limits, and mark the connection broken when reauthorization is genuinely required.
- Provider error text names internal fields, validation rules, and org configuration that no end user should see. Keep it in operator-facing logs, and give the submitter a plain outcome with a reference an operator can look up.
- An owner mapping can point at a user who has been deactivated or a queue that has been removed. Detect it, assign the configured fallback, and flag the mapping for correction rather than failing the create.
- Validation rules and required-field configuration change without warning after the mapping was built. A rejected lead must be retained locally in a failed state with the reason attached, and must be replayable once the mapping is fixed.
- When the org is unreachable, the app must still accept and store the lead. Queue the push, show it as pending on the record, and never lose the submission to the outage.
Definition of done
9
Definition of done
9- The destination object and field mapping are configurable per connected org.
- The mapping is validated against the org's current fields, required flags, and picklist values before it can be saved.
- The org's duplicate rules are respected and a duplicate response links to the existing record instead of erroring.
- Every created record has an owner, with a defined fallback when the mapped owner is inactive.
- Expired sessions refresh and API limits produce backoff, not lost leads.
- End users see a plain outcome while operators get the full provider error and a reference.
- Rejected leads are retained locally with a reason and can be replayed.
- 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
Postmark Transactional Email
Postmark Transactional Email
Send transactional email through Postmark on the right stream, with bounces tracked.
What it does
A Postmark delivery path that separates message streams, honours suppression, and retains provider identifiers for diagnostics.
How it works
- 1 Put Postmark behind the app's existing mail layer as one adapter, so no calling code constructs a provider-specific payload. This entry is an alternative to the other transactional email integrations, not an addition — pick one adapter and keep the mail layer identical.
- 2 Classify every outbound message as transactional or broadcast and bind that classification to the matching message stream at the mail layer, so the choice is made once and cannot be got wrong at an individual send site.
- 3 Send from the app's background-job system and persist the provider's message identifier on the record the moment it comes back, so a support question about one email can be answered without guessing.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/postmark-transactional-email
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.