RooQuiz Docs
Connectors & Automation

Connectors & Automation

Connectors push the leads and bookings your quizzes generate into the tools you already use — email, your own backend, Slack, or your email service provider. Find them under Connectors in the left sidebar.

Connectors are team-level: configure one and every quiz uses it. To let only certain quizzes fire a connector, narrow it with trigger scope.

The RooQuiz connectors page: connector cards grouped into Notify people, Send to systems and Sync audiences

The page groups everything by what it does:

GroupWhat's in it
Sending accountsGmail — connect a Gmail account as a sending service with Connect Gmail. See Email Sending Service
Notify peopleEmail, Slack
Send to systemsWebhook, Zapier
Sync audiencesKit
Book callsCal.com — brings bookings made from result pages back into RooQuiz. See Connect Cal.com

The five channels

ChannelWhat it's for
EmailSend a customizable notification to chosen recipients when an event fires — up to 3 per team
WebhookPOST to your own URL with an HMAC signature
SlackAuthorize the Slack app and post new leads to a channel
ZapierPaste a Catch Hook URL and reach thousands of apps
KitAdd new leads to Kit (ConvertKit) as subscribers and tag them, including by result

Each connector fires on the events you pick — new submission, new lead, booking created, cancelled or rescheduled — see Trigger events & scope. Each connector runs independently — disabling one does not affect the others. Per-channel setup is covered in The five channels.

Permissions and plan

Only the team owner or an admin can manage connectors. Other members get a no-permission notice, and the sidebar item isn't shown to them.

Email, Slack and Cal.com are available on every plan; Webhook, Zapier and Kit are Pro only. On a free team, selecting a Pro channel greys out the configuration area and offers an upgrade link.

What the connector card tells you

Each configured connector shows:

  • Enabled / Disabled — whether it's working.
  • Setup incomplete — OAuth finished but a channel or final step is still missing. These do not deliver.
  • Last delivery — when it last fired and how it went (success / failed).

After setting one up, hit Send test to confirm the other end really receives it, rather than finding out on your first real lead.

In this section

Want to pull data on your own schedule instead of receiving pushes? See the REST API and MCP integration.

On this page