Pipedrive recipes
Text a person when a deal moves stage, and add their reply to the deal as a note.
Two recipes for Pipedrive. Each names its trigger and the BlueBot step, lists the fields to map and says how to test it with your own number before anyone else gets a text.
How Pipedrive connects
- : BlueBot’s Zapier app has a Send Text action and instant triggers for incoming texts and every change of state.
- : BlueBot’s Make app sends texts and starts scenarios when a text comes in or changes state.
Text when a deal moves stage
| Part | What it is |
|---|---|
| Trigger | When a deal moves to a new stage in Pipedrive |
| Action | BlueBot’s Send Text action |
| Connects through |
Steps
- Start a Zap with Pipedrive’s trigger for an updated deal.
- Add a Filter by Zapier step for the stage you care about, such as Proposal Made.
- Add BlueBot’s Send Text action and map the person’s phone number to To.
Map the fields
| BlueBot field | Map it to |
|---|---|
| To | The person’s mobile number from Pipedrive. US numbers can leave off the +1. |
| Text | Hi {{first_name}}, I just sent over the proposal. Text me here with any questions and I’ll answer today. |
{{first_name}} in the text | Pipedrive’s first name field. |
| Metadata | source set to pipedrive, and record_id set to the record’s id, so the status and reply webhooks for this text can find the record again. |
| Service | Auto, the default: iMessage when the person uses it, otherwise SMS through your iPhone. |
Test it
Put your own number in To and press Test step. A text arrives on your phone from your own number, and Zapier shows the message BlueBot returned with state: "queued". Then map Pipedrive’s field back into To and turn the Zap on.
Add replies to the person as a note
| Part | What it is |
|---|---|
| Trigger | A text comes in (BlueBot’s message.received webhook) |
| Action | BlueBot’s Watch Incoming Texts module starts it, and Pipedrive takes the text |
| Connects through |
Steps
- Start a scenario from BlueBot’s webhook for incoming texts.
- Search Pipedrive for the person with the sender’s phone number.
- Add a note to that person with the words of the text.
Map the fields
| From BlueBot | Into Pipedrive |
|---|---|
| From | The phone number to find the person by in Pipedrive. It’s in E.164 (+15555550123); search by the last 10 digits if Pipedrive stores numbers another way. |
| Text | The words, for a note, a row or a message. Null when the person sent only a picture. |
| Received At | When it came in, in UTC. |
| Files | Pictures and voice memos. Each url works for an hour, so copy a file you want to keep. |
| Chat ID | Set when the text came in a group chat; null for a one-to-one text. |
Test it
Press Run once in Make, then text your BlueBot number from another phone you’ve texted through BlueBot before. The scenario runs with that text. BlueBot copies texts from people you’ve texted through it, unless you set Which chats to copy to Everything.
Before you turn it on
- Text only people who asked to hear from you. Anyone who replies STOP goes on your stop list, and BlueBot cancels texts to them.
- A text that can’t go yet waits with a hold rather than failing: quiet hours, your Mac away, a daily limit.
- on the integrations page says what else the two do together.