# Trigger Events & Scope

Source: https://docs.rooquiz.com/en/connectors/events

> Every connector fires on trigger events and is limited by scope — which quizzes may fire it. What each of the five events means, how to narrow a connector to specific quizzes, and the consent filter.

Each connector decides **when it fires** (events) and **which quizzes may fire it** (scope). The two are ANDed: the event must match *and* the source quiz must be in scope before anything is delivered.

## Trigger events

Every connector needs at least one event:

| Event                   | Fires when                                                                                                                             |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **New submission**      | Someone completes a quiz — **every** submission, including anonymous ones and repeat attempts by the same person                       |
| **New lead**            | Someone leaves their contact details with your team **for the first time**                                                             |
| **Booking created**     | A call booked from a result page stands. If the Cal.com event type requires confirmation, that is the moment you confirm it in Cal.com |
| **Booking cancelled**   | Either side cancels the call in Cal.com                                                                                                |
| **Booking rescheduled** | The call moves to a different time in Cal.com                                                                                          |

<Callout type="warning">
  **"New lead" fires once, the first time that person leaves their details.** The same person taking another quiz later does not fire it again, because leads are [deduplicated across quizzes](https://docs.rooquiz.com/en/leads#where-leads-come-from). If you want a notification on every submission, choose **New submission** instead.
</Callout>

<Callout type="info">
  **New submission** is sent once the result has been calculated, so the delivery always carries the score, level or result type.
</Callout>

<Callout type="info">
  Booking events only cover sessions that actually stand. A pending request, a declined request, or a pending request that is rescheduled or withdrawn fires **nothing** — downstream automations shouldn't act on a meeting that hasn't been agreed. Booking events also need the [Cal.com connector](https://docs.rooquiz.com/en/bookings/calcom); without it RooQuiz never hears about bookings.
</Callout>

## Trigger scope

Scope controls which quizzes may fire this connector:

* **All quizzes** — the default. Any event from any quiz in the team is delivered.
* **Specific quizzes** — only the quizzes you select fire it.

<Callout type="info">
  Scope is matched against **the quiz the event came from**. For "New submission", that's the quiz that was just submitted; for "New lead", that's the quiz where the person **first left their details** — not the most recent one they took.
</Callout>

A typical use: push your flagship lead-gen quiz to Slack so the team sees it instantly, and keep an internal quiz from bothering anyone.

## Combinations worth copying

| What you want                            | Events                          | Scope            |
| ---------------------------------------- | ------------------------------- | ---------------- |
| Everyone hears about a new client        | New lead                        | All quizzes      |
| Score every response in your own backend | New submission                  | All quizzes      |
| Only track the flagship quiz             | New lead                        | Specific quizzes |
| Get told when your calendar shifts       | Booking cancelled + rescheduled | All quizzes      |
| Sync leads into your ESP                 | New lead                        | All quizzes      |

<Callout type="info">
  Changing events or scope **only affects events from then on** — nothing is replayed.
</Callout>
