Calendly support

Last updated date:

Connect, reconnect, and troubleshoot Calendly without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the organization and event population Seedling should index.
  • Create a personal access token from an authorized Calendly owner or administrator.
  • Grant users:read, organizations:read, event_types:read, scheduled_events:read, and optional webhooks:read only.
  • Do not send Calendly credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Calendly access tokensCalendly's personal access-token documentation.

2. Connect Calendly

  1. In Seedling, open Connections and choose Calendly.
  2. Connect from workspace scope as a current Seedling workspace administrator.
  3. Enter the personal access token and optional account label; Seedling always calls the Calendly API.
  4. Seedling verifies the current user and organization before storing the workspace connection.
  5. Allow the first Calendly synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Calendly personal access token rejected
Confirm the calendly personal access token is active, was entered without surrounding whitespace, and belongs to the intended Calendly account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Calendly population as empty.
Wrong account or scope
Disconnect before retrying with the intended Calendly identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the token owner remains an active organization owner or administrator when organization-wide coverage is expected.
  2. Check event cancellation, rescheduling, organization membership, and the scheduled_events:read capability.
  3. Remember that staged webhook subscriptions are diagnostics and do not determine ordinary polling coverage.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement calendly personal access token for the same Calendly account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old calendly personal access token in Calendly.