Book meetings with your AI agent via Cal.com (Calendly coming soon)

How to enable the "Book meeting" tool (book_meeting, Crece plan) so your AI agent sends a Cal.com link; Calendly is coming soon. To book straight into the Omnifox calendar, from Lite.

Jul 11, 2026

Watch this step in the video · Services and appointments

Before you start: if you want the AI to book the appointment directly, without sending links, use the Omnifox Calendar: the agent checks open slots and books, moves or cancels appointments (check_availability, book_appointment and manage_appointment) on every plan, from Lite. That's usually the recommended option; see Native tools (III): book appointments and check availability.

"Book meeting" (book_meeting), which sends a link from an external provider, requires the Crece plan. Today it works with Cal.com (available). Calendly is coming soon: in Settings → Integrations its card shows as "Coming soon" and it can't be connected yet.

"Book meeting" lets the AI agent send the customer a scheduling link when they ask for a demo, a sales call, or any kind of meeting — no back-and-forth coordinating availability.

Requirements

  • Cal.com connected under Settings → Integrations (you paste your Cal.com API key). Calendly will be usable once it's out of Coming soon.
  • At least one active event type on the connected provider.
  • Crece plan or above.

If no integration is connected, the tool shows up locked in the agent editor with a button that takes you straight to connecting one.

Setup

  1. Connect your Cal.com account under Settings → Integrations (Calendly, once available).
  2. In the agent editor's Custom actions tab, enable "Book meeting".
  3. In the system prompt, tell the agent when to offer the meeting and, if you have several event types, which name to use for each case.

Tool parameters

  • event_name (optional): the meeting type's name ("Demo", "Discovery 30min"). Accepts a case-insensitive partial match. If omitted, it uses the first available event type.
  • note (optional): logged internally for analytics — the customer never sees it.

How it works at runtime

  1. The system resolves the workspace's active integration (today, Cal.com; once Calendly is available and connected, it will take priority).
  2. It looks up available event types (5-minute cache) and picks the one matching event_name, or the first one if none was specified.
  3. It sends the customer a message with the booking link, through the same channel as the conversation.
  4. Once the customer books a slot, the provider notifies Omnifox (an invitee-created webhook) and the message is marked as booked.

Example

If you have "Demo 30min" and "Onboarding 60min" set up in Cal.com, and your prompt says "if the customer asks for a demo, !book_meeting with event_name='Demo'", when the customer writes "I'd like to see the product in action" the agent recognizes the intent, runs the tool with event_name="Demo", and the customer gets the exact link for that event type, not the first one on the list.

Tips

  • If you only have one meeting type, your prompt doesn't need to specify event_name — let it use the default.
  • Name your event types clearly and uniquely in the provider ("Demo", "Strategy call") so name-matching works reliably.
  • Pair this tool with lead qualification: only offer the meeting once you've confirmed the customer is actually interested.

Troubleshooting

  • "The tool shows up locked": you don't have Cal.com connected — go to Settings → Integrations and connect it (Calendly is still coming soon).
  • "It always sends the same event type": check that the event_name in your prompt matches (even partially) the real name configured on the provider.
  • "The customer booked but it's not showing in Omnifox": the provider's webhook may take a few seconds to process; if it never updates, check that the integration is still connected with valid permissions.
Was this helpful?

Related articles

Message us on WhatsApp