Five Make scenarios we build around Pipedrive
These are the five scenarios we build most often. For each one: what starts it, what it does, what goes wrong in real accounts and how we catch it. You can also read them as a checklist for scenarios you already run.
| Scenario | Trigger and steps | What goes wrong | How we catch it |
|---|---|---|---|
| Ad leads into the right pipeline | A lead form from Meta or LinkedIn comes in. Make looks up the person and organisation, creates them if they are new and adds a deal to the pipeline that belongs to the campaign. | Every lead becomes a new person, even when they already exist. Field names differ per form. | Search on email first, create second. One field mapping per form, and an empty value falls back to a default. |
| A won deal creates a project in Asana | A deal moves to won. Make picks the project template from the deal type and copies scope, contact and agreed dates into the project. | Someone marks the deal won twice and you get two projects. | The project ID is written back to a field on the deal. If that field is filled, the scenario creates nothing new. |
| Invoice status from accounting back to the deal | Your accounting tool reports a paid or overdue invoice. Make finds the deal by invoice number and writes status and date into Pipedrive. | The invoice number is missing or wrong on the deal, so Make finds nothing. | The number is written to the deal when the invoice is created. If Make finds no deal, the owner gets an alert instead of silence. |
| Apollo enrichment for new organisations | A new organisation lands in Pipedrive. Make asks Apollo for data on the domain and fills only the fields Apollo is allowed to fill. | Apollo overwrites what a rep typed in, or fills a field with noise. | Rules per field: Apollo may fill empty fields, filled fields stay with people. A source field shows what came from Apollo. |
| Cold email replies become deals in Pipedrive | Someone replies to an Instantly email. Make creates a deal in Pipedrive with the email attached and a follow-up task for the owner. | An out-of-office reply becomes a deal too, and the pipeline fills with noise. | Only replies with a real status pass through. The rest stays in Instantly, and the sequence stops on any reply. |
How the connection works under the hood, with webhooks and the pitfalls per module, is in our guide connecting Make and Pipedrive. Which integrations you can set up without Make is on Pipedrive integrations.