Webhooks
Send signed, auditable event notifications to an authorized customer endpoint.
Connect your stack without losing control of the data.
Move approved registration, attendance, engagement and content outcomes into the systems your team uses. CRM and marketing connections, signed webhooks, embeds and live distribution each preserve their own access and delivery rules.
Product screenshot, the integration settings with CRM, webhook and embed connections
An interface is not an integration.
The point of an integration is not another logo in a directory. It is a dependable handoff: the right registration, attendance, engagement, replay, Evergreen, Simulive or on-demand fact reaches an authorized destination with its source and consent context intact.
CRM and marketing workflows support approved follow-up; signed webhooks carry event-specific changes; embeds bring eligible journeys into a customer page; live distribution reaches configured destinations. Delivery history, revocation and recovery matter as much as the initial connection. Ask Sales which named providers are verified for your workflow before committing to a vendor.
Signed webhooks carry approved, event-specific changes- Embedded experiences respect the same access decisions as hosted pages
- CRM and marketing handoffs preserve consent and provenance
- Named providers are listed only after connection and recovery are verified
Connection types
Choose the handoff the workflow needs.
Use the connection type that serves the job; specific providers and plan access must be confirmed.
Embeds
Bring registration or playback into an approved external page without bypassing access rules.
CRM
Pass governed person and account outcomes, webinar context and approved next actions into a verified CRM connection.
Marketing automation
Share human-approved segments, tags or outcomes with a verified campaign workflow while retaining consent and source evidence.
Live distribution
Send an authorized broadcast to a configured destination while keeping provider state and failure visible.
Governance
Consent, tenant scope, credentials, delivery history and erasure rules stay part of every connection.
Before the handoff
Confirm the connection before the workflow depends on it.
Name the outcome
Define the registration, attendance, engagement, content or approved next-action data that needs to move.
Verify the destination
Confirm the provider, credentials, tenant scope, plan access and consent rules before the connection is treated as available.
Operate the handoff
Keep delivery history, signatures, failures, revocation and recovery visible after the first successful connection.
Keep reading
Related pages.
Questions
Questions about integrations.
Which kinds of connection are supported?
Signed webhooks, hosted-journey embeds, CRM, marketing automation and live distribution connect eligible webinar outcomes to approved destinations. These handoffs can carry webinar context, approved segments, tags and supported registration, attendance, engagement or recorded-viewing facts. Specific providers and plan access must be confirmed.
Which named providers are verified?
Named providers are listed only after connection and recovery are verified. Ask Sales which providers are verified for your workflow before committing to a vendor.
Do embeds bypass access rules?
No. Embedded experiences respect the same access decisions as hosted pages.
How do webhooks work?
Signed webhooks send auditable notifications of approved, event-specific changes to an authorized customer endpoint.
How are consent and data handled in a connection?
CRM and marketing handoffs preserve consent and provenance. Consent, tenant scope, credentials, delivery history and erasure rules stay part of every connection.