Pipedrive Deal Creation
Turn a qualified lead or purchase into a Pipedrive person, organization, and deal.
What it adds
A flow that finds or creates the person and organization, then opens a deal associated with both in the configured pipeline.
What your agent is told to do
5
What your agent is told to do
5-
1
Resolve the person and the organization first, matching the person on the normalized email and the organization on its domain or name, and only then create the deal that references them.
-
2
Make the three creates a recoverable sequence. Record what succeeded after each step, so a failure at the deal stage resumes from the existing person and organization instead of creating a second set.
-
3
Let an admin configure the pipeline, stage, owner, currency, and how the deal value is derived, and validate every one of those against the account before the mapping can be saved.
-
4
Derive a deterministic deal key from the app record that triggered it, and check for an existing deal under that key before creating one. Repeated events for the same signal must find the deal, not open another.
-
5
Do not resolve stages, pipelines, or users by their display names at run time. Names are edited freely; store stable identifiers and re-validate them, and pause the mapping with a named error when one has disappeared.
Edge cases it handles
8
Edge cases it handles
8- Creating a deal before its person and organization exist leaves orphaned deals with no one to call. Resolve or create both, confirm the associations, and only then open the deal.
- Pipeline, stage, owner, currency, and value must all be chosen deliberately. A deal dropped into the wrong pipeline at a default stage with no value is invisible in forecasting and will be worked by the wrong person.
- The same app event fires more than once through retries, webhook redelivery, and user impatience. Without a deterministic key derived from the source record, one purchase opens three deals and inflates the pipeline.
- Saved mappings reference stages and users that get deleted or deactivated. Detect the missing reference, pause the mapping with a message naming what is gone, and hold events rather than assigning to whatever remains.
- A partial failure — person created, organization created, deal rejected — must be resumable from where it stopped. Persist progress per step so the retry completes the sequence instead of starting a new one.
- Rate limits and token expiry both interrupt a multi-step sequence mid-way. Back off and resume from the recorded step, and mark the connection broken when reauthorization is required rather than retrying indefinitely.
- Organization matching by name is unreliable — punctuation, suffixes, and abbreviations all differ. Prefer the domain, and where the match is ambiguous, create the deal against the person and flag the organization for a human.
- When the provider is unavailable, the app's own conversion must still complete. Queue the sequence, show its status on the source record, and give operators a way to retry it by hand.
Definition of done
9
Definition of done
9- Person and organization are resolved or created before any deal references them.
- Repeated events for one source record produce exactly one deal.
- Pipeline, stage, owner, currency, and value are configured and validated against the account.
- Deleted stages or deactivated users pause the mapping with a named error rather than defaulting.
- A partial failure resumes from the last completed step without duplicating earlier objects.
- Ambiguous organization matches are flagged rather than guessed.
- The app-side conversion completes and the sync status is visible and retryable.
- 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.