Operator
← All integrations
Calendly logo+GitHub logo

Connect Calendly to GitHub

Automate Calendly and GitHub with AI

Open source maintainers and hiring teams often take requests through Calendly and track follow up in GitHub. Operator.io points OpenClaw at both so a new booking can open an issue with the invitee answers, link the Calendly event URL on an existing pull request thread, and close the issue when the meeting is marked complete. Ask what is scheduled with a contributor this month and it lists Calendly events beside open GitHub issues that reference them.

It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.

What your agent can do with Calendly and GitHub

What your agent does in Calendly

  • Cancel scheduled event

    Tool to cancel a scheduled Calendly event by creating a cancellation record. Use when you need to permanently cancel an existing, active event. The cancellation will trigger notifications to all invitees.

  • Create Event Type

    Tool to create a new one-on-one event type (kind: solo) in Calendly. Use when you need to programmatically create a new event type for scheduling meetings.

  • Create One-Off Event Type

    Creates a temporary Calendly one-off event type for unique meetings outside regular availability, requiring valid host/co-host URIs, a future date/range for `date_setting`, and a positive `duration`.

  • Create scheduling link

    Create a single-use scheduling link. Creates a scheduling link that can be used to book an event. The link allows invitees to schedule up to the specified maximum number of events. Once the limit is reached, the link becomes inactive.

  • Create share

    Creates a customizable, one-time share link for a Calendly event type, allowing specific overrides to its settings (e.g., duration, availability, location) without altering the original event type.

  • Create single use scheduling link

    Creates a one-time, single-use scheduling link for an active Calendly event type, expiring after one booking.

All 51 Calendly actions →

What your agent does in GitHub

  • Abort Repository Migration

    Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.

  • Accept a repository invitation

    Accepts a PENDING repository invitation that has been issued to the authenticated user.

  • Add app access restrictions

    Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps...

  • Add a repository collaborator

    Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation ma...

  • Add assignees to an issue

    Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.

  • Add email for auth user

    Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the...

All 846 GitHub actions →

How it works

Tell the agent what you want to happen between Calendly and GitHub, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Calendly, works out what to do, and runs the matching action in GitHub without you mapping a single field.

You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.

Common questions about Calendly and GitHub

How do I connect Calendly and GitHub to Operator?
You authorize Calendly and GitHub once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
What can my agent do across Calendly and GitHub?
Tell it the job and it moves between Calendly and GitHub as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
Can my agent keep Calendly and GitHub in sync?
Yes. It can watch Calendly and act in GitHub, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
Do I need to build a workflow or write code?
No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

Calendly and GitHub integrations

Put your agent on Calendly and GitHub

Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.

Try for free