Yes. Krokul CRM integrates with Eventbrite. Each placed order for your seminar, conference or product day arrives in Krokul as a contact, the company from the attendee profile and a deal in the events pipeline, with the answers to your registration questions on it. Check-ins at the door and refunds come back to the same contact, so sales follows up with the people who actually came. Teams connect it through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks.
Automation platformsZapierMaken8nAlbato
A buyer books two seats for your partner conference. Eventbrite sends order.placed, and Krokul reads the Order with its attendees from the Eventbrite API. Each Attendee profile gives a name, work email, job title and company. Krokul finds or creates the contact by email, links the client company and opens one deal per order in the events pipeline. Both seats sit on that deal.
Custom questions such as "Fleet size" or "Which product are you evaluating" come back in the answers of each attendee. Krokul maps every question to a custom deal field once per event. The manager opens a deal that already says what the visitor wants to see at the stand.
When staff scan a badge at the entrance, Eventbrite sends attendee.checked_in. Krokul adds an activity "Attended" to the contact and creates a follow-up task for the deal owner with the next working day as the due date. Registered people who never checked in stay visible in a separate pipeline stage for a recording email.
An order.refunded event or a cancelled attendee writes a comment on the deal with the refund date. Open follow-up tasks for that person close, so nobody calls a visitor who withdrew. The affiliate code of the tracking link that sold a ticket becomes the deal source.
| Eventbrite | Direction | Krokul | When |
|---|---|---|---|
| Order (order.placed) | Eventbrite → Krokul | Deal in the events pipeline, external key on the deal | Each placed order |
| Attendee profile: name, email, phones, job title | Eventbrite → Krokul | Contact, matched by email | Same order |
| Attendee profile: company | Eventbrite → Krokul | Client company linked to the contact | Same order |
| Attendee answers to custom questions | Eventbrite → Krokul | Custom deal fields | Same order, by the question mapping |
| Check-in (attendee.checked_in) | Eventbrite → Krokul | Activity on the contact, follow-up task | Badge scanned at the door |
| attendee.updated, order.updated | Eventbrite → Krokul | Updated contact details and deal comment | Attendee or order data changes |
| Refund (order.refunded) | Eventbrite → Krokul | Comment on the deal, follow-up tasks closed | Order refunded |
| Affiliate code | Eventbrite → Krokul | Deal source | Same order |
Yes. Krokul integrates with Eventbrite through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.
Three contacts and one deal. Eventbrite keeps a profile per attendee inside the order, and Krokul links each colleague to the same client company and to the deal of that order.
Yes. A free registration is also an Eventbrite order, so order.placed fires and Krokul creates the contact and the deal. The deal amount stays empty when the ticket price is zero.
Yes. Attendees without attendee.checked_in by the end of the event stay in the stage for registered people, and the manager sends them the recording or the slides.
Ticket classes, payments, payouts and the badge scanner stay in Eventbrite. An Eventbrite webhook carries only a link to the changed object, so every update is read back from the Eventbrite API before Krokul writes it.
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.
Eventbrite is a trademark of Eventbrite, Inc. Krokul is not affiliated with Eventbrite.