Our team rotates owners from a list rather than using assignment rules. Can it do that?

Yes. Switch off the header and the create step accepts an OwnerId, and the guide shows a short rotation table you edit instead of Salesforce rules. Teams that already have assignment rules usually leave them in charge, because one place to change routing is easier than two.

What if the form name has no matching campaign?

The lead is still created and assigned. The campaign step is skipped and the Teams post says so. Add the form to the table when you create the campaign and every later lead is counted; earlier ones can be added to the campaign by hand in Salesforce.

Salesforce is unreachable when a form comes in. What happens?

n8n keeps the webhook payload with the failed execution, the error workflow posts the raw fields to Teams, and you re-run the execution once Salesforce is back. Webflow also keeps the submission in its form inbox.

We are on HubSpot or Pipedrive. Same package?

Not this one. The Typeform-to-HubSpot and Gmail-to-Pipedrive packages in this category cover those CRMs, and the Webflow trigger swaps in with one node. The assignment-rule and campaign-member steps are Salesforce objects and are not part of those packages.

Is there a Zapier version?

No. This one relies on a raw Salesforce API call for the assignment header and a three-way branch, which we have only built and tested on n8n and Make. Make's Salesforce API-call module carries the header on the same connection.

WfSFTMade to order

Lead capture & routing

Webflow form → Salesforce lead, assignment rules, campaign member, Teams alert

Webflow forms feed Salesforce leads, assigned by your rules and counted on a campaign.

Salesforce already knows how to assign a lead. The missing piece is the form fill. This workflow sends each Webflow submission in as a lead, lets your assignment rules pick the owner, and adds the lead to the Salesforce campaign that matches the form. Anyone Salesforce already holds as a lead or contact is updated or handed to their owner as a task, and the Teams sales channel gets each lead with its owner and record link.

How it works

Wf
Trigger
Form submitted on the site (form_submission webhook)
Webflow
if
Step 1
Normalise the fields for Salesforce
Webflow field names map to FirstName, LastName, Company, Email, Phone and Description; Salesforce insists on a last name and a company, so a blank one gets a placeholder you choose.
SF
Step 2
Look for the email in leads and contacts
Two SOQL queries on the cleaned email decide the branch: an open lead is updated, an existing contact gets a task for its owner, and no match goes on to create a lead.
SF
Step 3
Update the match instead of duplicating
An existing lead has the new message appended to its Description and a custom Repeat enquiry checkbox ticked; an existing contact gets a Task assigned to its owner with the message in the body.
SF
Step 4
Create the lead and let your assignment rules own it
The insert carries the Sforce-Auto-Assign header, so Salesforce runs your active lead assignment rule and picks the owner; LeadSource is Web, and the form name and message go in Description.
SF
Step 5
Add the lead to the matching campaign
Each Webflow form name is paired with a Salesforce Campaign ID in a short table; the lead is added as a Campaign Member with status Responded, so campaign reports count it.
T
Step 6
Post to the sales channel
Teams gets a channel message with name, company, the message, the owner Salesforce chose and the campaign, plus a direct link to the lead.

What changes once it runs

Salesforce owns the routing: the assignment rules you already maintain decide who gets each website lead, so nothing is configured twice.
Website enquiries are counted on a campaign, so campaign lead and conversion reports include them without a manual import.
An email Salesforce already holds updates the record or raises a task for its owner instead of creating a second lead.
The Teams post, with owner, campaign and record link, appears in the sales channel within a minute of the submission.
Webflow's form inbox and notification emails carry on as before.

What you get

n8n workflow export with the field map and the form-to-campaign table at the top.
A setup guide covering the Webflow token and webhook, the Salesforce Connected App, the assignment header and Teams consent.
Field-mapping sheet from your Webflow fields to Salesforce lead fields, with the required-field notes.
Recorded walkthrough of a test submission ending as an assigned lead, a campaign member and a Teams post.
Make scenario built to the same shape, using Make's Salesforce API-call module for the assignment header.

Before you start

A Webflow site on a paid Site plan with native Webflow forms (Starter caps submissions), plus a site token with forms:read and sites:write scopes.
Salesforce on an edition with API access; Enterprise and Unlimited include it, so check your edition if you are on Professional.
At least one active lead assignment rule (or a default owner as fallback) and one Salesforce Campaign per form you want counted.
One Salesforce user for n8n allowed to create leads, tasks and campaign members, plus a Connected App for OAuth (settings in the guide).
Microsoft 365 with a Teams channel for sales; an admin may need to consent to the permissions n8n requests.
n8n Cloud or self-hosted n8n reachable over HTTPS for the Webflow webhook.

Built for

Questions before you buy

Our team rotates owners from a list rather than using assignment rules. Can it do that?: Yes. Switch off the header and the create step accepts an OwnerId, and the guide shows a short rotation table you edit instead of Salesforce rules. Teams that already have assignment rules usually leave them in charge, because one place to change routing is easier than two.
What if the form name has no matching campaign?: The lead is still created and assigned. The campaign step is skipped and the Teams post says so. Add the form to the table when you create the campaign and every later lead is counted; earlier ones can be added to the campaign by hand in Salesforce.
Salesforce is unreachable when a form comes in. What happens?: n8n keeps the webhook payload with the failed execution, the error workflow posts the raw fields to Teams, and you re-run the execution once Salesforce is back. Webflow also keeps the submission in its form inbox.
We are on HubSpot or Pipedrive. Same package?: Not this one. The Typeform-to-HubSpot and Gmail-to-Pipedrive packages in this category cover those CRMs, and the Webflow trigger swaps in with one node. The assignment-rule and campaign-member steps are Salesforce objects and are not part of those packages.
Is there a Zapier version?: No. This one relies on a raw Salesforce API call for the assignment header and a three-way branch, which we have only built and tested on n8n and Make. Make's Salesforce API-call module carries the header on the same connection.

Nearby on the shelf

Whole catalog