Add webinar registrants to a Campaign
Webinar registrations create or update a Contact and add that person to the right Campaign as a member.
New submission on your webinar or event registration form
Create or update a Contact in Salesforce and add that Contact to a Campaign as a Campaign Member
One-directional. A submission triggers the action — nothing is written back into your form.
Campaign influence reporting only works if every registrant is genuinely a member of the Campaign. Doing that by hand means a CSV import after the event, by which time the follow-up has already gone to the wrong list.
Marketing teams running a webinar series lean on this because each session gets its own Campaign and its own form. Registrations arrive as members with a status of Registered, and switching them to Attended after the session is the only manual step left.
Setting it up
- 1
Create the Campaign in Salesforce first and copy its record ID. The Campaign Member step needs the ID, not the Campaign name.
- 2
Publish a registration form for this session. One form per Campaign — reusing a single form across sessions makes members impossible to separate afterwards.
- 3
In Zapier, set the trigger to "New Submission" and select that session's form.
- 4
Add a Salesforce Find Record step on Contact, searching by email, with create-if-not-found switched on. This is what makes repeat registrants update rather than duplicate.
- 5
Inside the create-if-missing section, map First Name, Last Name and Work Email, and put Company into the Account name so the Contact is not left unattached.
- 6
Add a second Salesforce action, Create Record on Campaign Member. Set Contact ID from the step above and paste in the Campaign ID from step one.
- 7
Set Member Status to Registered. Leave Attended for the update you make from the Campaign itself once the session has run.
- 8
Register once with a test address, confirm the Contact appears in the Campaign's member list, then turn the Zap on.
What maps where
Using the Webinar Registration Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Salesforce |
|---|---|
| First Name | Contact First Name |
| Last Name | Contact Last Name |
| Work Email | Contact Email, the key the Find Record step matches on |
| Company | Account name the Contact is filed under |
| Job Title | Contact Title |
| Anything you'd like us to cover? | Custom field on the Campaign Member, read before the session |
Variations worth knowing
"How did you hear about this webinar?" is already on the form. Map it to a custom field on the Campaign Member and the same Campaign can be broken down by channel, instead of spawning a separate Campaign for every ad and newsletter that drove signups.
Email Updates is a yes or no on the form. Map it to the Contact's opt-in field so registering does not quietly subscribe anyone. Membership of the Campaign is recorded either way — attending one session and consenting to marketing email are separate facts.
If something isn't arriving
Salesforce refuses to add the same Contact to a Campaign twice and returns a duplicate error. Nothing is lost, since they are already a member. Silence it with a Find Campaign Member search before the create step and a filter that continues only when nothing was found.
Company was left out of the create-if-missing mapping, or the name typed on the form matches no existing Account. Map Company across, and decide whether unmatched names should create an Account or land under a holding Account you tidy weekly.
Frequently asked questions
Should registrants be Leads or Contacts?
Contacts, when the Campaign is about people you already know or intend to keep. Leads suit cold registrants not yet attached to an Account. A Campaign holds both, so the choice reflects how your sales team works rather than any limit of the Zap.
Does attendance get marked automatically after the webinar?
No. The flow records a Registered member at signup and stops there. Attendance comes from your webinar platform, so update the member status from the Campaign in Salesforce or import the attendee list once the session has finished.
Can one registration form feed several Campaigns?
It can, with Zapier paths picking the Campaign ID from an answer such as a session chooser. A form per Campaign stays easier to maintain and makes the member list obvious, so use paths only when sessions genuinely share one signup page.
Related automations
- Create a Lead from every demo request
Each demo request becomes a Salesforce Lead with source and company filled in, ready for an SDR to work.
- Log quote requests as pipeline Opportunities
Inbound quote requests arrive as Opportunities at the right stage, with budget and scope already on the record.
- Open a Case from every help request
Submissions on your help form open a Salesforce Case with priority and origin set for assignment rules to route.
- Route partner applications into a review queue
Partner and vendor applications land in Salesforce as records in a review queue, not as forwarded email.
- Write NPS scores onto the customer record
NPS responses update the matching Salesforce Contact, putting the score and the comment on the customer record.
- Add newsletter signups to Zoho CRM as tagged contacts
Every newsletter opt-in becomes a Zoho CRM contact carrying a tag you can build a campaign list from.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free