Skip to main content
Back to Integrations
Calendly logo

Calendly

Inventory Calendly members and their roles, open and stale invitations, groups and their admins, every meeting type with its owner and the meeting tools it uses, routing forms, webhooks that send booking data to other systems, and the Enterprise activity log of who changed what.

Questions you can answer 15

Each one is a saved query that ships with ConfigView, reading your Calendly data on your own server. Ask it in plain English, SQL, Slack or the API.

  • Who changed Calendly users or roles in the last 30 days?
  • Show recent changes in the Calendly activity log
  • Who was added to or removed from Calendly this month?
  • Which Calendly members have left the company?
  • Who still has a Calendly seat but is deprovisioned in Okta?
  • Which Calendly users are not in Google Workspace?
  • Who are the Calendly owners and admins?
  • Who can create organization-wide webhooks in Calendly?
  • Which Calendly admins also administer a group?
  • Which Calendly invitations have been pending for over a month?

What ConfigView collects from Calendly 9

  • Activity Log

    Who changed what in Calendly (Enterprise plan): people added, removed or given a new role, sign-ins, event types and settings changed - with the time, who did it and their role. Kept as a growing history.

  • Event Types

    The meeting types people can be booked for: name, owner, whether it is active, hidden or managed by an admin, solo or team (round robin, collective), length, whether it takes payment, and which meeting tools it uses (Zoom, Google Meet, Microsoft Teams, Webex, phone, in person). Descriptions, notes, addresses, meeting links and booking questions are not stored.

  • Group Members

    Who is in each Calendly group and whether they are a group admin or a member, including invited people who have not joined yet.

  • Groups

    Calendly groups (Enterprise): each group's name and how many people are in it.

  • Invitations

    Invitations to join the Calendly organization: the email invited, whether it is still pending, was accepted or declined, and when it was sent and last re-sent.

  • Members

    Everyone in the Calendly organization: name, email, role (owner, admin or user), time zone, and when they joined.

  • Organization

    The Calendly organization: its name, plan (Standard, Teams, Enterprise and so on), whether it is on a trial, and which person's token ConfigView is using and that person's role.

  • Routing Forms

    Calendly routing forms - the forms that qualify a visitor and send them to the right person's calendar: name, draft or published, how many questions and whether they ask for an email or phone number. Answers people submitted are never read.

  • Webhooks

    Webhooks that send booking data out of Calendly to another system: organization-wide, group and personal webhooks, which events they send, whether they are active, who created them and the host the data goes to. The full URL and signing key are not stored.