Block 1 - Webflow Trigger
- Type / Role
- n8n-nodes-base.webflowTrigger - webflowTrigger
- Config choices
- Version 2
This workflow is provided as-is. Please review and test before using in production.
This n8n template automates the process of capturing leads from Webflow form submissions and syncing them with your Pipedrive CRM. It ensures that each submission is accurately associated with the ...
n8n-nodes-base.webflowtrigger, n8n-nodes-base.pipedrive, n8n-nodes-base.if, n8n-nodes-base.stickynote, n8n-nodes-base.code
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by PixelMakers.
Original n8n.io sourceThis n8n template automates the process of capturing leads from Webflow form submissions and syncing them with your Pipedrive CRM. It ensures that each submission is accurately associated with the correct organization and contact in Pipedrive, streamlining lead management and minimizing duplicates.
Sales teams that want to automate CRM data entry, marketing teams capturing qualified leads from landing pages, or any business looking to improve their Webflow-to-CRM integration workflow.
The workflow assumes that Webflow form submissions include the lead’s email address.
The domain is extracted from the email to match or create the organization in Pipedrive.
This template does not handle lead scoring or enrichment, but can be extended for such use-cases.
Extract website from email The email is split to extract the domain (e.g., [email protected] → company.com), which is used to search for existing organizations.
Check if the organization exists The Pipedrive API is queried using the domain. If the organization exists, we proceed. If not, a new organization is created.
Check if the person exists -- If the person already exists in Pipedrive, a note is added to their activities to log the form submission. -- If the person does not exist, a new person is created, a note is added to the person, and a new lead is created.
(Optional) Add your own actions You can extend this workflow to trigger Slack notifications, email follow-ups, or internal dashboards.
Start with the manual trigger node, or replace it with a webhook to connect directly to Webflow form submissions in real-time.
You can add enrichment services to auto-fill job titles or LinkedIn profiles. Perfect for growing sales pipelines without manual CRM input.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Sync leads from Webflow to Pipedrive CRM using n8n |
|---|---|
| Complexity | advanced |
| Nodes | 15 |
| Categories | CRM |
| Author | PixelMakers |
| Published | 23 Jun 2025 |
Use the JSON export at /data/workflows/5166/5166.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
This n8n template automates the process of capturing leads from Webflow form submissions and syncing them with your Pipedrive CRM. It ensures that each submission is accurately associated with the ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your CRM use case.