---
title: Integrations with People, Funnel, Outreach, Tasks and Notes
description: "What a booking does in the rest of Venom: the invitee becomes a contact with the meeting logged, the deal moves, Outreach stops, a follow-up task and a meeting note wait for you, and a link tied to a person fills the form in."
section: calendar
order: 35
audience: [user, builder, agent]
sources: [services/nodejs-cloud/lib/calendar/integrations.ts, services/nodejs-cloud/lib/calendar/integrations-model.ts, services/nodejs-cloud/migrations/0205_calendar_integrations.sql, services/nodejs-cloud/components/calendar/public/BookForm.tsx]
features: []
---

A booking in Venom Calendar knows the rest of Venom. When someone books one of your event types:

- **People** finds them among your contacts (by email, then phone) or adds them, and logs the meeting.
- **Funnel** finds their open deal, or opens one, and moves it to the stage you chose.
- **Outreach** stops their sequences that stop on a meeting.
- **Notes** writes a meeting note in your personal vault, with the agenda from their answers.
- **Tasks** gives you a follow-up after the meeting, or "Re-book" after a no-show.

Each event type has its own settings in `integrations`. People and Outreach are on by default; Funnel, Tasks and Notes
start when you set them. Set them with `PUT /api/workspace/calendar/event-types/{id}` or the `calendar_event_type_save`
tool ([below](#agents)). The event type editor in the [Calendar app](/docs/calendar/app.md) gets an Integrations section next.

```json
{
  "integrations": {
    "people": { "tags": ["booked-intro"] },
    "funnel": { "pipeline_id": "<pipeline id>", "on_booked": "<stage id>", "on_cancel": null, "on_no_show": "<stage id>", "create_deal": true },
    "outreach": { "booking_link": true },
    "tasks": { "due_business_days": 1 },
    "globe": { "folder": "Meetings" }
  }
}
```

## People

On by default. Turn it off with `"people": { "enabled": false }`.

When a booking is confirmed (at once, or when you confirm a pending one):

1. The invitee is matched against **your own** contacts by email, then by phone. Only exact handle matches count; names
   never do. A booking from a [link tied to a person](/docs/calendar/booking-pages.md#links-for-one-person) uses that person.
2. With no match, a new **private** contact is made with their name, email and phone. How you met says
   `Booked <event type> on <date>`, and the contact gets the event type's `tags`.
3. A **meeting** interaction is logged at the booking's time, with the event type and the answers. It links to the
   note in Venom Notes when there is one.

The booking keeps the person (`person_id`). A reschedule moves the interaction to the new time, a cancel rewrites it to
say so, and a no-show says "No-show".

| Field | Type | Default | What it does |
|---|---|---|---|
| `enabled` | boolean | `true` | `false` turns People off for this event type |
| `tags` | string[] | `[]` | tags a new contact gets (up to 20) |
| `ask_again` | string[] | `[]` | question ids always asked, even when an earlier answer is on file |
| `vip` | object or null | `null` | `{tag?, circle?, schedule_id}`: people with that tag or circle book against another schedule |

### Recognised invitees

A single-use link made for a person (`person_id` on the link) fills the form in: their name, email and phone from your
contact, and answers they gave in earlier bookings with you. Questions with an answer on file are skipped, except the
ones in `ask_again`. The skipped answers are sent with the booking as if typed.

A public page opened with `?email=` or `?name=` prefills just those values. It never looks the email up: anyone can
type an address, and a lookup would show who is in your contacts.

### VIP schedules

With `vip`, a link tied to a person who has the tag (any case) or is in the circle (`inner`, `active`, `longtail`) books
against `schedule_id` instead of the event type's schedule. Use it to give partners evening times without showing them
to everyone.

```json
{ "people": { "vip": { "tag": "partner", "schedule_id": "<evening schedule id>" } } }
```

## Funnel

On when `pipeline_id` is set.

On booking, the person's open deal in that pipeline is found (a link's own deal first). With none and `create_deal`,
a deal named `<person>, <event type>` opens, owned by you, with the person on it and `calendar:<booking id>` as its
source. The deal then moves to `on_booked`, and a note is logged on it by Venom Calendar. The booking keeps the deal
(`deal_id`).

A cancel moves the deal to `on_cancel`, and a no-show to `on_no_show`, when those are set.

| Field | Type | Default | What it does |
|---|---|---|---|
| `pipeline_id` | id | (required) | the pipeline the deal is in |
| `on_booked` | stage id or null | `null` | the stage on booking |
| `on_cancel` | stage id or null | `null` | the stage on cancel |
| `on_no_show` | stage id or null | `null` | the stage on a no-show |
| `create_deal` | boolean | `false` | open a deal when the person has none in the pipeline |
| `gate` | stage ids or null | `null` | a link tied to a deal books only while the deal is in one of these stages |
| `enabled` | boolean | `true` | `false` turns Funnel off and keeps the settings |

### Deal gates

With `gate`, a single-use link tied to a deal shows times only while the deal is in one of the gate stages. Outside them
the page says "This link isn't open yet". A "Kickoff" event type with `"gate": ["<Closed-won stage id>"]` can then only
be booked after the deal is won. A link that already booked is not checked again, so a retried submit still gets its
confirmation.

## Outreach

On by default. Turn it off with `"outreach": { "enabled": false }`.

A booking stops the person's active and paused enrollments whose sequence stops on a meeting (`stop_on.meeting`), with
the stop reason `meeting`. If Outreach can't be reached, the booking says "Outreach not available" and stands.

### Booking links in drafts

Set `"booking_link": true` on one event type. Outreach drafts can then write `{{booking_link}}`: each draft gets a fresh
single-use link to that event type for the person (and the deal, when the enrollment has one), valid for 30 days. A link
tied to the person also [fills their form in](#recognised-invitees). The first active event type with `booking_link`
is used, and it needs your booking profile.

## Tasks

On when `tasks` is present. Needs the Tasks add-on.

When a booked meeting has ended, the next sweep (every few minutes) makes a Tasks issue for you:
"Follow up with <name> (<event type>)", due `due_business_days` business days (Monday to Friday) after the meeting's day
in your time zone. With a deal, it is a to-do on the deal; otherwise it goes to `team` (or your first team) and links
the person and the meeting note. After a no-show it is "Re-book <name> (<event type>)" instead. Each is made once,
whatever happens to the booking after.

| Field | Type | Default | What it does |
|---|---|---|---|
| `due_business_days` | integer 0 to 30 | `1` | business days after the meeting the issue is due |
| `team` | team key or id | your first team | where the issue goes when there is no deal |
| `enabled` | boolean | `true` | `false` turns Tasks off |

## Notes {#globe}

On when `globe` is present. Needs the Notes add-on.

On booking, a note is made in your **personal** vault at `<folder>/<yyyy-mm-dd> <name>` (a second one the same day gets
` (2)`), with:

- when it is, and a mention of the person (the same chip as typing `@` in Notes)
- the deal and its stage, and a link back to the booking
- the agenda: the invitee's answers
- what you know: role and company, when you last spoke, the open deal and the warmth score
- empty **Notes** and **Next steps** headings

The note is made once. A reschedule doesn't make another one.

| Field | Type | Default | What it does |
|---|---|---|---|
| `folder` | string | `Meetings` | the folder in your personal vault |
| `enabled` | boolean | `true` | `false` turns Notes off |

## Your confirmation

Calendar's own confirmation to you adds what you know about the person: their role and company, when you last spoke,
their open deal and stage, and the warmth line from [keep-warm](/docs/cloud/people-keep-warm.md). It shows only what People
lets you see: for a contact another member shares with the org, the name, role and company, never their notes or
interactions.

## When an integration fails

Each integration runs on its own. One that can't run (no add-on, a pipeline that was deleted, no Tasks team) never fails
the booking and doesn't stop the others. The reason is kept on the booking in `integrations.problems`, the newest five
per integration, and `calendar_booking_get` lists them.

```json
{
  "integrations": {
    "person_id": "…",
    "person_created": true,
    "interaction_id": "…",
    "deal_id": "…",
    "outreach": "stopped",
    "note": { "id": "…", "path": "Meetings/2026-11-12 Dana Lee", "href": "/globe/vault/…" },
    "followup": { "issue_id": "…", "identifier": "SAL-42" },
    "problems": [{ "integration": "tasks", "message": "No such team.", "at": "2026-11-12T03:05:00.000Z" }]
  }
}
```

## Agents

No new tools: `calendar_event_type_save` takes `integrations` as above and lists every problem with it at once, and
`calendar_booking_get` shows what the integrations did.

## Related

- [Booking pages](/docs/calendar/booking-pages.md): links, holds, reschedule and cancel
- [People](/docs/cloud/people.md) and [Funnel](/docs/funnel.md)
