Yes. Krokul CRM integrates with ON24. Registrants of your ON24 webcasts arrive in Krokul as contacts with a company and a deal, live and on-demand attendance is added to the same contact, and questions asked during the webcast turn into tasks for the deal owner. A manager can register a client for an upcoming webcast from the deal. Teams connect it through the Krokul app in Zapier, or through the Krokul API with an ON24 API token.
Automation platformsZapier
A head of operations registers for your ON24 webcast on warehouse automation. Krokul reads the new registrant through the ON24 REST API for that event, finds the contact by email and links the client company. The deal opens in the webcast pipeline with the event title as its source. No form handling is needed on your site.
After ON24 finalizes attendance, Krokul reads the attendees of the event and writes an activity on each contact, marked live or on-demand. A registrant who watched moves to the stage for follow-up calls. A registrant who never joined gets a task to send the replay link.
A viewer types a question about pricing in the ON24 console. Krokul picks it up with the attendee record, adds it as a comment on that deal and creates a task for the owner to answer within the working day. The answer goes out from Krokul, with the question in view.
A customer success manager wants a key account at next week's product briefing. From the deal, the manager chooses the ON24 event, and Krokul creates the registrant through the ON24 API. The client receives the ON24 confirmation, and the deal shows the registration.
| ON24 | Direction | Krokul | When |
|---|---|---|---|
| Registrant of an event | ON24 → Krokul | Contact, client company and deal in the webcast pipeline | Each poll after a registration |
| Attendee, live | ON24 → Krokul | Activity on the contact, deal stage | After ON24 finalizes live attendance |
| Attendee, on-demand | ON24 → Krokul | Activity on the contact | After ON24 processes on-demand viewing |
| Registrant without attendance | ON24 → Krokul | Task to send the replay | After attendance is final |
| Audience question | ON24 → Krokul | Comment on the deal and a task | With the attendee record |
| Registrant (create) | Krokul → ON24 | Contact on a deal | A manager registers a client |
Yes. Krokul integrates with ON24 through the Krokul app in Zapier and through the ON24 REST API with the Krokul API and webhooks.
Yes. Krokul marks each attendance as live or on-demand. On-demand viewing reaches Krokul later because ON24 processes it after the live data.
The page itself can stay where it is. Each registration still has to reach ON24 through the registrant endpoint, one call per event, and Krokul reads it from there like any other registrant.
Access to the Registration endpoints and the Event-level Analytics endpoints. A token with access to all endpoints also works.
Webcast production, the audience console, content and engagement analytics stay in ON24. Per the ON24 REST API overview, registrant data is available within about 15 minutes, live attendance 30 minutes to 2 hours after the event ends and on-demand viewing 4 to 12 hours later, so attendance reaches Krokul on that schedule.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
ON24 is a trademark of ON24, Inc. Krokul is not affiliated with ON24.