Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.servicebooked.ca/llms.txt

Use this file to discover all available pages before exploring further.

ServiceBooked is the AI receptionist; the integrations connect it to where the rest of your work happens.

Calendar integrations

Three options for booking, covered in detail in the Calendar section:
  • Google Calendar — direct OAuth, real-time availability + booking
  • Cal.com — open-source scheduler with webhooks for booking sync
  • Calendly — paste your link; the AI hands customers off
Pick whichever matches what you already use.

Slack

Pipes notifications to a Slack channel — useful for teams who live in Slack and want a real-time feed of leads / bookings / cancellations.

Connect

Settings → Integrations → Slack → Connect. OAuth flow takes you to Slack’s auth page; approve, and you’re connected.

Pick a channel

The integration UI shows a dropdown of channels in your workspace. Pick where notifications should post (defaults to #general). Private channels require you to /invite the ServiceBooked bot before they show up in the dropdown.

Pick events

Toggle which events fire Slack notifications:
  • New lead — every contact created
  • New conversation — every fresh inbox conversation
  • Form submission — every form filled out
  • Appointment booked — every new appointment
  • Appointment cancelled
  • Appointment completed
  • Negative feedback received — when a customer leaves 1-3 star feedback (useful for fast response)
Most teams enable new lead, appointment booked, and negative feedback. The rest is noise.

Disconnect

Same screen. Removes our bot from your workspace; notifications stop.

Outgoing webhooks

For piping events into your own systems (custom CRM, internal dashboards, Zapier, etc.):

Add a webhook

Settings → Integrations → Webhooks → Add webhook:
  • URL — your endpoint
  • Events to subscribe to — pick from the same event list as Slack
  • Signing secret — we generate one; you use it to verify requests are actually from us

What gets sent

Every subscribed event POSTs a JSON payload to your URL with:
  • event_type — e.g. appointment.booked
  • timestamp — ISO 8601 UTC
  • organization_id
  • data — the event-specific body (contact info, appointment time, etc.)
Headers include X-ServiceBooked-Signature, an HMAC-SHA256 of the body using the signing secret. Verify on your end before processing.

Retries

Currently fire-and-forget — no automatic retry on failure. If your endpoint is down, the event is lost. A retry queue with backoff is on the roadmap. For production-critical use cases, consider a queueing layer (your own webhook receiver that buffers + retries) until we ship retries natively.

Disable

Toggle off any webhook from the same page. The endpoint stops getting events immediately.

Zapier (via webhooks)

You can plug ServiceBooked into Zapier indirectly:
  1. Set up a Zapier “Webhook trigger” — Zapier gives you a URL.
  2. Add that URL as an outgoing webhook in ServiceBooked.
  3. Subscribe to relevant events.
Now Zapier sees every ServiceBooked event and can fan out to any of its 5000+ integrations (Sheets, QuickBooks, Mailchimp, etc.). A native Zapier app is on the roadmap.

Email sender

This isn’t an integration in the traditional sense — it’s the email delivery configuration. By default we send branded emails from a noreply@servicebooked.ca address with your business name as the From name. White-label customers can configure a fully branded sender (e.g., mike@jonesplumbing.com) by setting up DNS records that authorize us. Talk to support.

ICS feed

Read-only calendar feed of your appointments. See ICS feed for setup.

What’s NOT supported (yet)

Not all integrations exist. As of today, no native:
  • QuickBooks / accounting tools
  • Salesforce / HubSpot direct sync
  • Mailchimp / email marketing tools
  • Job-management software (Jobber, Housecall Pro, ServiceTitan)
For most of these, the workaround is webhooks → Zapier → target tool. If you need a native integration with one of these, the support team tracks demand and we sometimes prioritize based on it.

Next

Notifications

Per-user notification preferences for the in-app bell + email digests.