> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getnexor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Calendly

> Connect a supported Calendly account, map team hosts, and let a Nexor booking Agent use an event type or scheduling link.

Connect Calendly when Calendly should own the booking page, event duration, and availability. Configure the Agent with a Calendly event type or link. When Calendly creates a booking and the connected webhook receives it, Nexor mirrors it into the meeting flow.

<Info>
  Direct Calendly booking by the Agent depends on the environment. Some legacy configurations can share a saved Calendly link, but link sharing is not a guaranteed fallback for every per-host setup. Confirm the actual behavior on your account with a test booking and do not assume either path before activation.
</Info>

<Warning>
  The current integration requires a Calendly **Teams** or **Enterprise** plan. Owner or Admin access is required to connect, re-sync, map hosts, or disconnect it.
</Warning>

## Before you connect

Confirm that:

* The Calendly account uses a supported Teams or Enterprise plan.
* The person connecting can authorize the intended Calendly organization.
* The recurring event types you plan to use are active in Calendly.
* Nexor workspace members already exist for the hosts you want to map.

Calendly and Nexor's native Google or Outlook booking are different provider paths. Calendly controls its own availability. Native booking uses each Nexor host's connected calendar and weekly availability.

## Connect Calendly

<Steps>
  <Step title="Open the integration">
    Go to **Integrations** and find **Calendly** under **Calendar & Scheduling**.
  </Step>

  <Step title="Start the connection">
    Select **Connect** and complete the Calendly authorization flow.
  </Step>

  <Step title="Check the status">
    Return to **Integrations → Calendly**. Confirm that the page shows the connected state, plan, connection date, and last sync.
  </Step>

  <Step title="Configure the booking Agent">
    Open an Agent with the **Book a Meeting** goal, then go to **Settings → Meeting** and choose **Calendly** as its type.
  </Step>
</Steps>

If the page shows **Calendly Teams or Enterprise required**, reconnect with a supported organization or update the Calendly plan. If Nexor reports a webhook or connection error, select **Reconnect** before relying on new bookings.

## Choose how leads book

In the Agent's **Meeting** section, choose **Calendly**. Under **Book via Calendly**:

1. Leave **Host** on **Assign automatically**, or choose a default Nexor member.
2. Under **How leads book**, choose **Event type** or **Custom link**.
3. For **Event type**, select an active recurring Calendly page.
4. For **Custom link**, paste the full Calendly scheduling URL.
5. Save the Agent and run a test booking. Confirm that the account either shares a working link or completes the booking directly before activation.

Calendly supplies the duration and available times, so Nexor does not show its native duration control for this type.

<Note>
  A default host is a routing preference, not a guarantee for every Calendly configuration. In a round-robin event, Calendly chooses the actual host. Nexor uses the booking webhook as the final source for that organizer.
</Note>

## Enable team hosting

On the Calendly management page, **Team hosting is off** appears until an Owner or Admin enables it.

After selecting **Enable team hosting**, the page lists:

* Calendly users and their connection status.
* The Nexor member mapped to each Calendly user.
* The meeting configurations associated with each host.
* Agents that currently use Calendly.

Map each Calendly host to the matching Nexor member. Use the same person's account on both sides so that meeting ownership and lead assignment remain understandable.

<Warning>
  In the current release, do not rely on assigning a different Calendly event type to each host from the Agent settings. That per-host save path is not operational end to end. Use the Agent-level event type or custom link and verify one real test booking before activation.
</Warning>

## Re-sync or reconnect

Use **Re-sync** after changing Calendly users, event types, or organization membership. Review the new sync time and the host mappings afterward.

Use **Reconnect** when the status says the webhook or authorization is unavailable. New bookings may not mirror into Nexor while the connection is degraded.

## Disconnect Calendly

Only an Owner or Admin can disconnect the integration.

<Steps>
  <Step title="Review Agents that use Calendly">
    On the management page, check the Agent bindings and move any active booking Agent to another supported provider first.
  </Step>

  <Step title="Disconnect">
    Select **Disconnect**, review the confirmation, and continue.
  </Step>

  <Step title="Verify the fallback">
    Open each affected Agent and confirm its meeting type, hosts, calendar connection, and availability before accepting new leads.
  </Step>
</Steps>

Disconnecting stops future Calendly synchronization. Historical meeting data already stored in Nexor remains available.

## Verify a test booking

Create a real test booking through the same event type or link the Agent will send. Confirm:

* The booking appears in **Meetings** with **Booked via Calendly**.
* The date, time, lead, and actual host are correct.
* The event appears in Calendly.
* The intended reminders are configured in [Reminders and alerts](/docs/en/guides/meetings/reminders-and-alerts).
* Cancelling or rescheduling follows the intended Calendly and Nexor path.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The account connects but the plan is rejected">
    The integration requires Calendly Teams or Enterprise. Confirm the organization and plan used during authorization, then reconnect.
  </Accordion>

  <Accordion title="An event type does not appear">
    Confirm that it is an active recurring event type in the connected organization. Select **Re-sync** and check again. You can use a verified full Calendly URL under **Custom link** when appropriate.
  </Accordion>

  <Accordion title="The wrong host receives a round-robin booking">
    Calendly is authoritative for the actual round-robin host. Review the event type's host pool in Calendly and the Nexor host mappings, then make a new test booking.
  </Accordion>

  <Accordion title="A new booking does not appear in Nexor">
    Open **Integrations → Calendly** and check for a degraded webhook or authorization state. Reconnect if prompted, then verify the Agent binding and event type.
  </Accordion>
</AccordionGroup>