Connect Calendly to Rig

    Rig syncs your Calendly event types, scheduled events and organisation memberships into your warehouse, so booking volume sits next to pipeline data. You connect with a personal access token and your organisation URI.

    Before you start

    • You need a Calendly account. If you are an organisation admin, your token gives access to Calendly data for everyone in the organisation. A member's token covers only their own data.
    • You need to look up your organisation URI, which is the current_organization value returned by Calendly's GET https://api.calendly.com/users/me call.

    Step 1: Create a Calendly personal access token

    1. In Calendly, open the Profile menu, choose Developer, then Personal access tokens.
    2. Select Create personal access token and name it.
    3. Choose every scope Rig needs to read: the ones that cover your user details, event types, scheduled events and organisation memberships. A token without them is refused on those requests. Then select Create.
    4. Enter the verification code Calendly emails you.
    5. Copy the token and store it securely.

    Step 2: Find your organisation URI

    1. Call GET https://api.calendly.com/users/me with your token as a bearer token. The Calendly developer docs show how tokens are used.
    2. In the response, copy the current_organization value. It looks like https://api.calendly.com/organizations/AAAA....

    Step 3: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Calendly, open the card and click Connect.
    3. Personal Access Token: The token you created.
    4. Organization URI: The full current_organization value, including https://.
    5. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    6. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Calendly lands in its own calendly schema in your warehouse:

    • Event types: The meeting types people can book.
    • Scheduled events: Each booked meeting with its time, status and host.
    • Organisation memberships: The users in your Calendly organisation.

    Good to know

    • An admin's token reads the whole organisation, while a member's token sees less, so use an admin's token if you want company-wide bookings.
    • Calendly sends an emailed verification code when you create a token, so have access to that inbox first.
    • Rig reads scheduled events and event types, so invitee-level answers are not part of this connection.
    • To disconnect Calendly, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Measure meeting booking volume and conversion
    • Track cancellation rates
    • Analyse the demo and sales meeting pipeline
    • Balance rep booking load

    More ideas for using Calendly

    Calendly documentation

    Was this guide helpful?