How the Pipedrive Asana integration works
The integration listens for one event in Pipedrive: a deal marked as won. From there it runs a fixed sequence. This is the sequence we build:
- Trigger. A deal is marked won. Pipedrive sends a webhook to the integration.
- Pick the template. The integration looks at the deal type or the product on the deal and picks the matching project template in Asana. An audit gets a different template than an implementation.
- Create the project. The project lands in the right team, with the owner and the deal fields filled in. Tasks get their due dates from the agreed start date.
- Write back. The project ID and link go back to a field on the deal. Marking the deal won a second time does not create a second project.
- Status back to the deal. When the phase or risk changes in Asana, the integration updates the deal. Sales sees in Pipedrive how the project runs, without digging through Asana.
| Deal field in Pipedrive | Where it lands in Asana | Why |
|---|---|---|
| Scope and products | Project description and the chosen template | The team knows what was sold. |
| Contact and organisation | Project fields | The team knows who the point of contact is. |
| Agreed start and delivery dates | Project dates and task due dates | Planning starts from what the client was told. |
| Deal value | A project field, visible in the portfolio | You see which projects weigh the most. |
| Deal owner | A project field and a follower on the project | The team knows who made the promises. |
Make or our own middleware? Usually we build the integration as a Make scenario. It is quick to set up, you see every step and you can change it yourself. We pick our own middleware when volume is high, when each template has many rules or when an error must never mean a missed project. That middleware runs on our own infrastructure, with a queue and error handling. The downside is that you cannot change it yourself in an editor. Which other integrations Pipedrive offers is on Pipedrive integrations.