INTEGRATIONS
Webinar integrations: what Webinly connects to, and what each connection does
Webinly connects to Stripe, Tap and Tabby for payments, GoHighLevel for contacts, Teachable for course access and Google Calendar for booked calls, and sends signed webhooks to anything else. Here is what each connection does, where you switch it on, and which plan it needs today.
What a webinar actually needs to connect to
In Webinly the registration page, forms, booking pages, emails, the room and the CRM with lead scoring are one product, so a registrant is a contact the moment they sign up, with no tool in between where a lead can go missing. What is left to connect is what lives outside: your payment processor, your ad platforms, a CRM your team already runs, your course school, your calendar and your own systems.
Every integration at a glance
Everything except the API and ad pixels is listed on the Integrations page in your dashboard. “Every plan” means Starter, Pro and Scale.
| Integration | What it does | Set up in | Who can use it |
|---|---|---|---|
| Stripe | Card payments into your own Stripe account. The one-click upsell and downsell in the room need it. | Settings, Payments | Every plan |
| Tap | Card payments on your own Tap account, including KWD and SAR prices. | Settings, Payments | Every plan |
| Tabby | Pay in 4 on offers priced in AED, SAR or KWD. | Settings, Payments | Every plan, with your own Tabby merchant account |
| GoHighLevel | Contacts from the webinars you choose sent to one sub-account, tagged registered or attended. | Integrations, then each webinar | Every plan |
| Teachable | Enrolls buyers of an automated webinar's offer in the course it unlocks. | Integrations | Every plan |
| Kajabi | Gives buyers of an automated webinar's offer the Kajabi product it unlocks. | Switched on by the Webinly team | Per account, on request |
| Google Calendar | Busy times block booking slots; bookings land in your calendar. | Scheduling, Calendars | Every plan |
| Ad pixels | Meta, TikTok, Google Analytics 4 and Google Tag Manager events from your webinar pages and forms, plus Microsoft Clarity recordings, for every visitor who has not declined cookies. | Settings, Tracking | Every plan |
| Webhooks | Signed event data sent to your own HTTPS address. | Integrations, Webhooks | Every plan |
| REST API | Webinars, registrations, analytics, contacts, deals and bookings, with keys that carry only the scopes you tick. | Settings, Developers | Scale |
| Custom domain | Your webinar pages served on a domain you own. | Integrations, Custom domain | Scale |
WhatsApp from your own number is connected from the same page. Then, in Automations, name for each webinar a message template approved on your WhatsApp account that takes the first name, the webinar title and the watch link, and send yourself a test there to check the name. Anyone who registers with a phone number but never opens the room then gets one WhatsApp message with their watch link 7 minutes after their session starts, a delay you can change for that webinar in Automations (2 to 180 minutes). People who left no phone number get nothing, so ask for one on the registration form if you plan to use it.
Payments: Stripe, Tap and Tabby
Stripe and Tap take card payments at the checkout inside the webinar room, on the offer page your follow-up emails link to, and on forms that end in a payment, into your own account with each processor.
- Stripe
Press Connect Stripe in Settings, Payments and finish Stripe’s own sign-up and verification; the page lists anything Stripe still needs before you can take payments. The one-click upsell and downsell after a purchase in the room charge the card the buyer just used, and they run on Stripe only.
- Tap
Paste the secret key and public key from your Tap dashboard. The public key draws the card form inside the room. Before you sell with a live key, Tap has to register Webinly’s app domain for your account; the Payments page tells you what to ask, and test keys work straight away. Webinly does not offer KWD or SAR prices through Stripe, so selling in those currencies needs a Gulf processor such as Tap.
- Tabby
Paste your Tabby secret key and merchant code. On an offer priced in AED, SAR or KWD, buyers see Pay in 4 beside the card option, and Tabby’s own page opens in a popup while the room keeps playing. Tabby never replaces the card checkout: with no card processor connected, it is not offered.
Prices and fees are on the pricing page.
Connect your webinar to a CRM
Webinly is a CRM already: every registrant becomes a scored contact with a timeline and a lifecycle stage. If your sales team works somewhere else, there are three ways to get webinar leads there.
The GoHighLevel webinar integration
Connect HighLevel on the Integrations page and choose the sub-account when HighLevel asks. Then, in each webinar you want synced, switch on Sync to GoHighLevel in the Engagement step (Live room, for a live webinar). The switch appears once HighLevel is connected and starts off.
Each registrant of a free webinar is created or updated in that sub-account with their name and email, tagged registered when they sign up and attended the first time they join the room, so your HighLevel automations can start from either. Someone who pays to register, or is added through the API, reaches HighLevel only when they first join the room, tagged attended, so on a paid webinar start your HighLevel automations from that tag. An optional prefix, such as spring-launch, is added as its own tag so several funnels can share one sub-account. Scores, stages and bookings stay in Webinly.
Webhooks, for any other CRM
HubSpot, Salesforce and other CRMs have no built-in connection. Send the New registration webhook to your own endpoint instead: it carries the name, email, phone and custom answers the person gave, the webinar and session they chose, their UTM tags, and the page they came from. From your registration pages it covers free webinars only. If people pay to register, subscribe the same endpoint to Purchase / payment completed too: paying for a seat sends that event instead, with the buyer’s name, email, phone, UTM tags and the page they came from.
The API, on Scale
Pull registrations with an API key, or add people to a webinar from your own systems. If all you need is each new lead in your CRM as it arrives, the webhook is the simpler route: nothing to schedule or poll, and the registration reaches you the moment it happens.
Webinar webhooks
A webhook is a message Webinly sends to an address you own the moment something happens. Add an endpoint on the Integrations page: an HTTPS URL, an optional label, and the events you want. Leave every event unticked to receive all of them. The events you can pick include:
| Event | Sent when |
|---|---|
| New registration | Someone registers for a free webinar on its page, or is added to any webinar through the API. A repeat registration with the same email is not sent again. Paying to register sends Purchase / payment completed instead. |
| Purchase / payment completed | A buyer pays for an offer inside the webinar or on its offer page, or for a seat at a paid webinar. The one-click upsell and downsell after an offer, and payments taken on forms, do not send it. |
| New booking, Booking cancelled, Booking rescheduled, Booking marked completed | The matching change on one of your booking pages. |
| Deal won, Deal lost, Deal moved to a new stage | The matching change on your CRM board. |
Signed deliveries. Each delivery is a JSON POST (event, created_at, data), signed with a secret shown once when you create the endpoint. The Webinly-Signature header carries a timestamp and an HMAC-SHA256 of the timestamp and body, in the same t=...,v1=... format Stripe uses, so your endpoint can reject forged or replayed messages.
Test before it matters. Send test fires a clearly marked test event. Each endpoint shows its last success or failure and why, and can be paused, edited or deleted.
One attempt each. Deliveries are not retried. Your endpoint has 5 seconds to answer; if it is down or slow, that event is missed. Private network addresses are refused.
The REST API, on Scale
On Scale, create API keys in Settings, Developers. Each key gets only the scopes you tick, so a key for a dashboard can be read-only. Keys can expire after 30 days, 90 days or a year. Calls send the key as a Bearer token; a call the key has no scope for is refused with a 403. If the account leaves Scale, its keys stop working.
Keys can list webinars; read registrations and analytics; read contacts, deals and pipelines; read your scheduling events, available times and bookings; create registrations, for example from a form on your own site; create and cancel bookings; and manage webhook subscriptions, which deliver exactly like the ones on the Integrations page.
Courses, calendars and your domain
- Teachable
Paste your Teachable API key and school address on the Integrations page. On an automated webinar, pick the course in the offer’s Delivers list in the engagement studio. The buyer is enrolled the moment they pay and emailed how to log in. Offers on a live webinar have no Delivers list, so their buyers are not enrolled automatically; plan to give them access yourself after the session.
- Kajabi
Kajabi products appear in the same Delivers list, on automated webinars only, but Kajabi is not self-serve: the Webinly team switches it on for an account when you ask.
- Google Calendar
In Scheduling, under Calendars, choose which Google calendars count as busy and which one receives new bookings for your booking pages.
- Custom domain, on Scale
Open the Custom domain tile on the Integrations page, add a domain you own, such as webinars.yourbrand.com, and create the DNS record Webinly shows you. Every webinar in the account is then served on it.
What it does not do
No Zapier app. Webinly has no public app in Zapier’s directory. Registrant to CRM, buyer to course and booking to calendar are built in or covered above.
No HubSpot, Salesforce or Mailchimp connection. Use the webhooks, or the API on Scale.
No Typeform or Calendly connection today. Webinly Forms and Webinly Scheduling do those jobs on the same contacts. Outlook and Apple calendars cannot be connected either.
GoHighLevel is one-way and per webinar. Nothing comes back from HighLevel, booking pages do not push to it, a form reaches it only when it registers someone for a synced webinar, people who pay to register or are added through the API reach it only when they first join the room, tagged attended, and a push HighLevel refuses is not shown in Webinly.
Webhooks fire once, and not for every payment. No retries, and no delivery history beyond each endpoint’s last success or failure. The one-click upsell and downsell after an offer, and payments taken on forms, send no webhook, so do not fulfil those orders from Purchase / payment completed.
Ad pixels do not wait for a yes. They fire for every visitor who has not declined cookies, including anyone who never answers the cookie banner. If the law where your audience lives requires consent before tracking, weigh that before you add a pixel.
Common questions
- What integrations does Webinly have?
- Stripe, Tap and Tabby for payments; GoHighLevel for contacts; Teachable for course access, with Kajabi switched on per account on request; Google Calendar for booking pages; Meta, TikTok, Google Analytics 4, Google Tag Manager and Microsoft Clarity for tracking; and outgoing webhooks. The Scale plan adds the REST API and a custom domain.
- How do I connect my webinar to a CRM?
- Registrants already land in Webinly's own CRM with scores and stages. For GoHighLevel, connect it on the Integrations page and switch on Sync to GoHighLevel in each webinar. For any other CRM, use the New registration webhook, plus Purchase / payment completed if people pay to register, or the API on Scale.
- Does Webinly integrate with GoHighLevel?
- Yes. Registrants of the webinars you choose are created or updated as contacts in one HighLevel sub-account, tagged registered when they sign up and attended when they first join the room, with an optional prefix tag. People who pay to register, or are added through the API, are sent only once they join, tagged attended. Data only goes from Webinly to HighLevel.
- Does Webinly have webhooks?
- Yes, on every plan: registration, payment, booking and deal events, each sent as a signed JSON POST to your HTTPS address. Deliveries are not retried, so answer within 5 seconds.
- Which integrations need the Scale plan?
- The REST API and the custom domain. Payments, GoHighLevel, Teachable, Google Calendar, ad pixels and webhooks work on every plan.
- Does Webinly connect to HubSpot, Salesforce or Zapier?
- Not directly. There is no built-in HubSpot or Salesforce connection and no public Zapier app. The New registration webhook carries the details of everyone who registers free on a webinar's registration page to a tool of your own, Purchase / payment completed does the same for people who pay to register, and on Scale the API does the same on request. People a form sends to a webinar's recording do not trigger New registration.
Connect the tools you keep
Payments, contacts, courses and your calendar from one page, with webhooks for the rest.
Your card is saved when you pick a plan. On a first plan the first charge is 14 days later, with one webinar and 50 registrations in between. Cancel any time from the billing page.
Related reading
- Webinar CRM and lead scoring: what happens to a registrant inside Webinly before any integration.
- Customer data platform: contact profiles, plus CSV import and export for moving a list in or out.
- Offers and checkout inside a webinar: where Stripe, Tap and Tabby are used, and the upsell ladder.
- Gulf payment methods for trainers: KNET, mada and Apple Pay, and how to connect Tap.
Last updated 2026-09-27. Every connection, event and plan on this page was checked against the product that day. Something out of date? Email us.
One product, every part connected.
- Offers and checkoutTimed offers they pay for without leaving the room.Offers and checkout: how it works
- CRM and lead scoringDeals, calls, and who is ready to buy.CRM and lead scoring: how it works
- Customer data (CDP)One profile per person, every action in it.Customer data (CDP): how it works