Nedzo workflows can now start from Pipedrive. When something changes in Pipedrive, your workflow runs, and it can take different paths based on Pipedrive data. Your AI calls and texts fire when your CRM changes, instead of when someone remembers.
You know how this goes. A rep adds a new lead to Pipedrive, then gets busy, and nobody follows up for two days. By then the lead has gone cold. Now the follow-up starts the moment the lead shows up.
Pipedrive workflow triggers
Your workflow can start when:
- Someone adds a person in Pipedrive
- Someone updates a person in Pipedrive (you can narrow this to one field or label)
- A person enters the Pipedrive filter you sync with Nedzo
The last one has a catch. Pipedrive doesn't send an event when someone joins a filter, so Nedzo picks it up on its daily check or the next time that person changes.
Branch on Pipedrive data
Inside a workflow, you can split the path on a Pipedrive label or on the value of a person field. Nedzo reads that data from your synced contact, so it doesn't have to wait on Pipedrive.
An example
Say you add the label "Hot lead" to a person in Pipedrive. That counts as a person update, so your workflow starts and checks the label. Hot leads get an AI call right away, and everyone else gets a text. After the conversation, the workflow writes a note and labels back to the person in Pipedrive, so your reps see what happened without leaving Pipedrive.
Pipedrive follow up automation, both ways
Nedzo already synced contacts with Pipedrive in both directions, and workflows could already write notes and labels back to a Pipedrive person. Now Pipedrive can start the workflow too. Nedzo does the calling and texting, and the result goes back to Pipedrive.
It's live in your account now.