Marketing Automation · Integration
ON24
Add ON24 to your product for your customers, and give your AI agents governed access to it.
Embed an ON24 integration so your customers can run and measure their webinar programme from inside your product. ON24 holds webinars and on-demand events, the registrants and attendees against them, and the engagement detail that makes the platform worth integrating: attendance and viewing time, poll and survey answers, questions asked and resources downloaded. A product event on your side can register someone or add them to an audience, and the engagement that follows comes back as data your product can act on, delivered per tenant. Each customer authorises their own ON24 account, so nothing is pooled through a shared key. fastn owns the credentials, retries, rate limits and API upkeep, and the same governed connection is what your AI agents read.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Register a contact for a customer's webinar from an event in your product so signup follows what a user actually did.
Let each customer connect their own ON24 account so registrant and attendance data appears inside your product with no per-customer code.
Read engagement detail per attendee, including viewing time, poll answers and resources taken, so scoring in your product reflects real behaviour.
Push webinar outcomes onward to the CRM or marketing platform a customer already runs, through the same governed connection.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises who attended a webinar, how long they stayed and what they asked, reading only that tenant's account.
An agent flags the most engaged attendees for follow-up and explains why, with every read audited.
An agent registers a contact for an upcoming session within scoped permissions, with the write attributed.
Example prompt
Who were the most engaged attendees at yesterday's ON24 webinar, and what did they ask?
Set up ON24 in 4 steps
- 01Enable the ON24 connector in your fastn dashboard.
- 02Have each customer supply credentials for their own ON24 account so calls run under their access.
- 03Map the webinar, registrant and engagement fields your product uses, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the ON24 integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an ON24 integration without building it. Your customers connect their own ON24 account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an ON24 update is not your on-call problem.
- One integration serves your product and your agents. The same governed ON24 connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
GoTo Webinar
MarketoWorks well with
HubSpotOften used alongside
Tools the same teams tend to run next to ON24, across other categories.
Salesforce
Pipedrive
Zoho CRM
ApolloON24 integration FAQ
How do I add an ON24 integration to my product?
Enable the ON24 connector in your fastn dashboard, then let each customer authenticate their own ON24 account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ON24 client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own ON24 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own ON24 account and only ever sees their own campaigns, segments and subscribers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this ON24 integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent summarises who attended a webinar, how long they stayed and what they asked, reading only that tenant's account.
Who maintains the ON24 integration?
fastn does. When ON24 changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I trigger an ON24 campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from ON24?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the ON24 integration?
A common starting point: register a contact for a customer's webinar from an event in your product so signup follows what a user actually did. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the ON24 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ON24 does not change your per-connector cost. You can start free with 3 connected accounts.
Add ON24 to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.