Calendly integration

Calendly connected to your WhatsApp, without leaving the chat

Connect your Calendly account from Settings → Integrations and you're set in one click: your agents (or your AI agent) send the booking link as just another WhatsApp, Instagram, or website chat message. When someone books or cancels, Omnifox notes it and tags that conversation automatically.

7 days free. No credit card.

1 clic
to connect your Calendly account
2
Calendly events Omnifox listens for on its own
0
webhooks you have to set up by hand
The basics

What it actually does the Calendly integration

The usual problem with Calendly and WhatsApp is that they stay disconnected: the agent copies the link by hand, pastes it into the conversation, and if the customer books or cancels, nobody on the team finds out until they check Calendly separately.

Omnifox's integration with Calendly is genuinely native, not a webhook workaround you build yourself: you authenticate with your Calendly account from Settings → Integrations and Omnifox subscribes on its own to your organization's booking and cancellation webhook. There are no keys to copy or URLs to paste into Calendly's panel.

From there, any agent has a button in the chat composer to send the booking link (picking the event type if you have several), and the AI agent can do it on its own with the book_meeting tool. When the customer books or cancels in Calendly, Omnifox automatically stamps an internal note and a tag on that conversation.

In one sentence

Connect your Calendly once, and from then on the booking link goes out as just another chat message — sent by an agent, or sent by the AI on its own.

  • One-click OAuth connection, no manual webhooks
  • The link goes out as a chat message on any channel
  • Bookings and cancellations get logged and tagged automatically
  • The AI agent can offer and send the link without anyone touching it
Why it matters

What your team gains by connecting Calendly

The same event types you already set up in Calendly, now inside the conversation.

A button in the composer

Any agent can send the booking link without leaving the conversation, picking the event type (demo, discovery, follow-up) if you have several set up in Calendly.

The AI can send it too

The AI agent has a native tool, book_meeting, to offer and send the booking link on its own when the customer asks to schedule. Available from the Crece plan up.

Bookings and cancellations get logged automatically

When someone books or cancels in Calendly, Omnifox adds an internal note and a tag ("Booking confirmed" or "Booking cancelled") to the contact's conversation, without anyone typing it by hand.

Works on any channel

The link is sent as a normal text message, so it works the same on WhatsApp, Instagram, Messenger, Telegram, or your website chat.

No webhooks to set up by hand

The Calendly webhook subscription is registered by Omnifox on its own, the moment you connect your account. For this part, you don't need n8n or the API.

It filters your inbox for you

Since the booking gets tagged, you can filter your inbox to see who booked or cancelled without opening every conversation one by one.

How it connects

Calendly up and running in three steps

There's no need to create an app in Calendly's developer panel or generate keys — it's your usual account.

1

Connect your account

Go to Settings → Integrations → Calendly and authorize with your account. Omnifox stores the token and refreshes it on its own before it expires.

2

The webhook registers itself

Once you authorize, Omnifox subscribes to your Calendly organization's booking and cancellation webhook. There's nothing to copy or paste into any panel.

3

Send the link from the chat

From the composer, the booking button lets you pick the event type and sends it as a message. If you have an AI agent with book_meeting enabled, it can do it on its own too.

4

Check it in the conversation

When the customer books or cancels, the note and the tag appear on their own in that conversation — no need to go check Calendly separately.

The question we get asked

Do I stick with Calendly, or use Omnifox's own calendar?

Both paths are real. Neither one is the right answer for everybody, so here's what each one gains and gives up.

AVAILABLE TODAY

Stick with Calendly, connected

If you already use Calendly and your event types are set up there, you don't migrate anything: the connection on this page already does what matters — sending the link from the chat and logging the booking on its own.

  • No new learning curve
  • Availability and timezone handling are still Calendly's job
  • Bookings and cancellations get logged and tagged automatically in Omnifox
  • No automatic WhatsApp reminder out of the box: you build one with a workflow triggered by that tag
IN THE WORKS

Omnifox's own calendar (Citas)

We're building our own appointments module: multiple calendars, public booking without relying on a third party, Google Calendar sync, and automatic WhatsApp reminders. It already runs in production for Omnifox's own organization while we finish it, and it isn't open to customers yet.

  • Automatic reminder 24 hours before, fired on its own
  • Public booking page with your own branding
  • Two-way sync with Google Calendar
  • Automatic waitlist when a slot opens up
  • Not yet available for customer accounts: write to us if you want in first
FOR CUSTOM CASES

Your own webhook + n8n or your API

If you need something the native integration doesn't cover — like a WhatsApp reminder calculated from the appointment's exact time — build your own path: a workflow triggered by the tag we already add, or Calendly's webhook connected directly to n8n or our REST API.

  • Use the tag we already add as a workflow trigger, no code required
  • Or listen to Calendly's own webhook separately, with the exact event time
  • 125 operations and a dedicated trigger in the n8n nodes
  • The same path Shopify or HubSpot use for what isn't native
Worth knowing beforehand

What this integration doesn't do yet

We'd rather you know this now than the day you need it.

It doesn't create the calendar event

Omnifox doesn't manage availability or time slots — Calendly still handles that, on its own hosted booking page. What Omnifox does is send that link over chat and listen for when it's confirmed or cancelled.

It doesn't send a WhatsApp confirmation on its own

When someone books, Omnifox annotates the conversation and tags it — it doesn't automatically message the customer. If you want a confirmation message or a reminder before the appointment, build a workflow triggered by that tag, or use Calendly's own webhook with n8n or your API if you need the exact time of the event.

The AI agent requires the Crece plan

Having the AI offer and send the link on its own (the book_meeting tool) is a feature of the Crece plan and up. Connecting Calendly and sending the link by hand from the composer has no such requirement.

Our own calendar isn't open to customers yet

Omnifox has its own appointments module — with automatic reminders, public booking, and Google Calendar sync — but it's still being built and today only runs for Omnifox's own organization. In the meantime, Calendly remains the available path.

One Calendly account per workspace

The connection is saved per workspace, tied to the account of whoever authorized it. If different teams use different Calendly accounts, each workspace connects its own.

Cal.com is native too, just in case

If you use Cal.com instead of Calendly, there's also a native integration: the same button to send the link from the chat and the same AI tool.

If Omnifox's own calendar is exactly what you need, write to us: who asks for it first is what decides when it opens up.

FAQ

Frequently asked questions

No. It's a native integration: you authenticate with your Calendly account from Settings → Integrations, and Omnifox registers the booking and cancellation webhook for you. You don't need n8n for this part.
Omnifox adds an internal note to that conversation with the event and the time, and tags it ("Booking confirmed" or "Booking cancelled") so you can filter your inbox. It doesn't send any automatic message to the customer.
It can offer and send the Calendly (or Cal.com) booking link during the conversation, using the book_meeting tool, available from the Crece plan up. It doesn't create the calendar event itself — the customer picks the time slot on Calendly's own page.
Yes, and it isn't just a plan — it exists in the code, with public booking, automatic WhatsApp reminders, and Google Calendar sync. Today it only runs for Omnifox's own organization while it's being finished; it isn't open to customers yet. If you're interested, write to us.
The Calendly integration doesn't do that on its own. Today's path is to build a workflow in the visual editor triggered by the "Booking confirmed" tag, or connect Calendly's webhook directly to n8n or the API if you need the exact event time to calculate when to send it.
Yes. Cal.com has its own native integration with the same behavior: a button to send the link from the chat and the same AI tool.
Any channel where you have an open conversation with the contact: WhatsApp, Instagram, Messenger, Telegram, or your website chat. The link goes out as a normal text message.
Yes. If you have several active event types in Calendly (for example, Demo, Discovery, Follow-up), you choose which one to send from the composer, or tell the AI which one to use and it will.

Another question? [email protected]

Connect your Calendly and send it over WhatsApp without leaving the chat

One click to authorize, zero webhooks to set up by hand. 7-day free trial, no card required.

Message us on WhatsApp