%20(2).svg)
.avif)
How to Send Leads from Webflow to folk CRM Automatically
To send leads from Webflow to folk CRM automatically, you have three options: folk's Zapier integration (fastest), a Make scenario, or an n8n workflow calling the folk API directly (most control). All three follow the same shape — Webflow form submission → webhook → create or update a person in folk → add them to the right group.
| Method | Setup time | Dedupe | Best for |
|---|---|---|---|
| Zapier (folk's native app) | ~10 min | “Create or update person” handles email match | Quick start, low volume |
| Make | ~20 min | Search-then-branch pattern | Multi-step flows (Slack alert, enrichment) |
| n8n + folk API | ~30 min | Full control via API search | Custom fields, group logic, self-hosted stacks |
Option 1 — Zapier
Trigger: Webflow → New Form Submission. Action: folk → Create or Update Person (match on email), then a second action Add Person to Group for your pipeline group. Map hidden UTM fields to folk custom fields so source data arrives with the lead.
Option 2 — Make
Same trigger via the Webflow module, then folk → Search person by email → router: found → update + add note; not found → create person → add to group. The explicit search step is what keeps repeat submitters from duplicating.
Option 3 — n8n + the folk API (full control)
Point your Webflow form (Site Settings → Forms → webhook, or a form-specific fetch) at an n8n Webhook node, then call folk's REST API:
// n8n HTTP Request node — upsert a person in folk
POST https://api.folk.app/v1/people
Authorization: Bearer {{FOLK_API_KEY}}
{
"fullName": "{{ $json.name }}",
"emails": ["{{ $json.email }}"],
"companyName": "{{ $json.company }}",
"customFieldValues": {
"Source": "{{ $json.utm_source || 'organic' }}",
"Campaign": "{{ $json.utm_campaign }}",
"Message": "{{ $json.message }}"
},
"groups": [{ "id": "{{ INBOUND_GROUP_ID }}" }]
}
Before the create, add a search call (GET /v1/people?email=...) and branch: if the person exists, update and drop a note instead of creating — the same upsert discipline as any CRM. Grab your API key and group IDs from folk → Settings → API, and check folk's current API docs for exact field names on your plan.
Finish the workflow with a Slack alert containing the lead's context and a link to the folk record — speed-to-lead matters more than the tool choice.
Want to apply this to your setup?
Which one should you pick?
Zapier if you want it running today and volume is low. Make if the lead should trigger 3–4 downstream steps. n8n if you're already self-hosting automations or need custom field logic folk's native apps don't expose. The dedupe pattern — search by email before creating — is non-negotiable in all three.
Q: Does Webflow integrate with folk CRM natively?
A: There's no direct Webflow–folk app inside Webflow, but folk's Zapier integration plus Webflow's form triggers gives you a supported no-code path in about ten minutes; Make and the folk REST API cover everything beyond that.
Q: Can I keep my UTM attribution when sending leads to folk?
A: Yes — capture UTMs into hidden form fields (see our UTM capture guide) and map them to folk custom fields in your Zap, scenario, or n8n payload.
Want your lead flow wired end to end?
We build Webflow lead pipelines into folk, HubSpot, Salesforce, and most modern CRMs — dedupe, attribution, routing, and alerts included — as part of our Webflow automation services. Tell us about your project.
Related: The full lead capture automation architecture · Webflow HubSpot Integration
