Turn form signups into ready leads inside Pipedrive. When someone completes your Typeform, their company, contact, and lead records appear in minutes. Great for sales teams that want clean data without manual entry.

An event from Typeform starts the run. A Set node standardizes answers and keeps only the fields you need. A Code node converts the selected company size into the exact Pipedrive option ID for a custom field, so data lands in the right place. The flow then creates an Organization, links a Person to that org, opens a Lead, and attaches a Note with key answers and the company size. Reps get context and structure right away, which speeds up follow up and reduces mistakes.

Connect a Typeform account and a Pipedrive account. Replace the form ID, confirm the Pipedrive custom field key for company size, and update the option IDs if your account uses different values. Expect faster first touch, fewer errors, and a simple handoff to the team. This is a good fit for demo requests, partner inquiries, and B2B contact forms where company size helps qualify.

• Typeform on form completion trigger starts the run as soon as a user submits
• Set node cleans and standardizes input while keeping only the mapped fields
• Code node translates company size labels into Pipedrive option IDs for a custom field
• Create Organization in Pipedrive with the company size stored in a custom property
• Create Person with email and link it to the new organization
• Create Lead tied to both the person and the organization
• Create Note on the lead that includes key questions and the selected company size

• Reduce manual lead entry from 20 minutes to 2 minutes per form
• Streamline intake by up to 80 percent with zero copy paste
• Improve data accuracy by mapping the exact Pipedrive field options
• Connect Typeform and Pipedrive so both tools stay in sync
• Handle up to 10 times more submissions without extra admin work
• Keep CRM records clean with auto linked org person and lead

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Typeform and Pipedrive. See the Tools Required section above for links to create accounts with these services.
3. Open the Typeform trigger node. In the Credential to connect with menu, click Create new credential and follow the on screen steps to connect your Typeform account. Choose the form you want or paste the form ID where the node shows [UPDATE ME].
4. In the Set node, review each field mapping. Make sure the question labels match your Typeform exactly. If your form uses different wording, update the field names so the values map correctly.
5. In Pipedrive, create or locate an Organization custom field for company size. Copy its field key. In the Create Organization node, replace the sample custom field key with your own field key.
6. Update the Code node that maps company size. Make sure each size label from your Typeform maps to the correct Pipedrive option ID for that custom field. If needed, fetch option IDs from Pipedrive using their API or your admin settings.
7. Open each Pipedrive node (Create Organization, Create Person, Create Lead, Create Note). In the Credential to connect with menu, click Create new credential, then enter your Pipedrive API token from your Pipedrive account settings.
8. Save the workflow and enable it. Submit a test response in your Typeform with a valid email, company name, and company size selection.
9. In Pipedrive, confirm a new Organization exists with the company size custom field set. Check that a Person and a Lead were created and linked to the same organization.
10. Open the Lead and verify a Note was added. The note should include the key questions and the chosen company size.
11. If nothing arrives in Pipedrive, recheck the Typeform form ID, confirm the trigger is connected, and ensure both credentials are valid. If company size is blank, adjust the Code node mapping or the custom field key.
12. Once validated, adjust copy in the Note content or add more mapped fields in the Set node to capture extra context.