The event platforms connector links CRM campaigns to the platforms where you run your webinars and events: Livestorm, Eventbrite, Zoom Webinars and Microsoft Teams webinars. An event's registrants and attendees are added to the campaign automatically; people unknown to the CRM become leads; each attendance becomes an activity in the person's timeline. The screen is reserved for administrators.
Each platform is enabled separately: for instance, you can use Livestorm for webinars and Eventbrite for trade shows. Without the connector, campaigns remain usable and participations are entered manually on the campaign record.
Set up a platform
- In the Vault, create a secret for each key or application secret. A key is never typed into the connector screen.
- Open Event platforms connector, enable the platform and fill in its details:
- Livestorm: the secret holding the API key (Livestorm account settings, integrations, public API);
- Eventbrite: the secret holding the private token; the organization is optional (empty: the account's first organization);
- Zoom: a Server-to-Server OAuth app from the Zoom Marketplace, with read scopes for webinars and reports; enter the account ID, client ID and client secret; for webhooks, the app's Secret Token; the host is optional;
- Microsoft Teams: an Entra ID application with the
VirtualEvent.Read.Allapplication permission; enter the tenant, the application ID, its secret and the webinar organizer.
- Save, then Test connections: each enabled platform shows its result.
Register the webhooks
After saving, the screen shows the webhook URL of each platform that sends webhooks (Livestorm, Eventbrite, Zoom). Register it in the platform's webhook settings:
- Eventbrite: order placed, attendee updated, attendee checked in, order refunded;
- Zoom: registration created, approved, canceled or denied, participant joined, webinar ended. Zoom validates the URL as soon as it is registered;
- Livestorm: registrations and session end.
The URLs contain a secret token: do not share them. Regenerate token makes the old URLs unusable; you must then register them again. Teams does not send webhooks: its registrations and attendance are read periodically. Without webhooks, the scheduled sync is enough, with a delay of a few minutes.
What reaches the CRM
- On a campaign record, the Event card links the campaign to an event on a platform. An event feeds only one campaign.
- Registrants become campaign members with the "registered" status, attendees with the "attended" status. Once the event is over, registrants who did not come move to "no-show".
- A known person is matched to their contact or lead; otherwise a lead is created, with the "event" source and the campaign. Marketing consent is recorded only if the person ticked it on the registration form: it is never presumed.
- Each attendance becomes an activity (completed meeting) in the person's timeline.
- A status never goes backwards: an attendee does not become registered again. A cancellation returns a registrant to "invited" and creates no one.
- Syncs run every 15 minutes for events starting within 30 days, in progress, or ended less than 14 days ago. The Sync now button runs one immediately.