Typeform lead to a Pipedrive deal
Each enquiry from your Typeform becomes a person and a deal in Pipedrive, and Slack hears about it.
Typeform → Pipedrive → Pipedrive → SlackA pipeline is only as honest as the last update someone typed. Bizomate creates people, organisations and deals when a form is filled in or an order is placed, moves deals between stages, logs activities and notes, and starts a workflow the moment a deal is added, updated, won or lost. Every run leaves a record of what it changed.
| Label | Value |
|---|---|
| Plans | ◇ Paid plans — on Free you can build and test; publishing needs a paid plan |
| Connect | An API token |
| Starts runs | Instantly |
| Kind | Connected app · CRM/Sales |
In every pipeline, or the one you choose. Set up with Pipedrive when you publish.
Set up with Pipedrive when you publish.
Set up with Pipedrive when you publish.
A call, meeting or task. Set up with Pipedrive when you publish.
Any field, or only the fields you name; the run gives what they were before. Set up with Pipedrive when you publish.
Won, lost or either, in every pipeline or one. Set up with Pipedrive when you publish.
With the fields from your own Pipedrive account, custom ones included, required ones first.
By the fields you give, a status, or a filter saved in Pipedrive; up to 1,000.
Choose the pipeline, then the stage.
With its quantity, price and discount; left empty, the price is the product's own.
Finds the person by email and updates them, or adds them if there is nobody.
Finds the organisation with exactly that name and updates it, or adds it.
Leads, notes and products. A lead needs a person or an organisation.
Any kind: deal, person, organisation, activity, lead, note or product.
Links a deal or lead to a person or organisation, or a person to an organisation. A deal or lead has one of each, so linking replaces the one it had.
Pipedrive is a premium connection. On any plan, Free included, you can add it and build and test workflows that use it; publishing one of those workflows needs a paid plan.
No. Publishing a workflow with a Pipedrive trigger adds the webhook for you, with its own user name and password, and unpublishing or deleting the workflow takes it away. Each published workflow has its own.
Yes. Each step reads the fields from your own Pipedrive account, custom ones included, required ones first. A choice takes its label, a user their email, and a person, organisation or stage its id.
Use Create or update a person: it finds the person by the email you give, updates them if they are there, and adds them only when there is nobody. Create or update an organisation does the same by the organisation's exact name, and Create or update a record by a field whose values are unique, such as a product's Product code.
Each enquiry from your Typeform becomes a person and a deal in Pipedrive, and Slack hears about it.
Typeform → Pipedrive → Pipedrive → SlackWhen a deal is won, the onboarding task is waiting in Asana and the team is told.
Pipedrive → Asana → Slack