Per-pair page

Calendly + GitHub: turn user-research bookings into issue context.

Create GitHub issues for follow-up work from Calendly research interviews, demo bookings, or office-hours sessions. Captures customer signal as engineering work.

Connect Calendly and GitHub See reverse direction

Trigger app

Calendly as the trigger

Workflows fire when something happens in Calendly.

Invitee CanceledWebhook
New Meeting BookedWebhook

Action app

GitHub as the action

Workflows do something in GitHub, instantly.

See all 23 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Calendly → GitHub

When something happens in Calendly, do it in GitHub.

2 Calendly triggers wired to 23 GitHub actions. Most-used pairing: Invitee Canceled → Add Labels.

GitHub → Calendly

Or fire it the other way around.

1 GitHub triggers wired to 5 Calendly actions downstream.

New GitHub Event

See GitHub → Calendly →

Popular pairings

Common Calendly → GitHub workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 8 of 46 combinations

When invitee canceled in Calendly, add labels in GitHub.

Fires when a Calendly meeting is canceled by the invitee or host. Use to clean up CRM activity, release Zoom resources, or prompt a reschedule.

When invitee canceled in Calendly, create comment in GitHub.

Fires when a Calendly meeting is canceled by the invitee or host. Use to clean up CRM activity, release Zoom resources, or prompt a reschedule.

When invitee canceled in Calendly, create issue in GitHub.

Fires when a Calendly meeting is canceled by the invitee or host. Use to clean up CRM activity, release Zoom resources, or prompt a reschedule.

When invitee canceled in Calendly, create pull request in GitHub.

Fires when a Calendly meeting is canceled by the invitee or host. Use to clean up CRM activity, release Zoom resources, or prompt a reschedule.

When new meeting booked in Calendly, add labels in GitHub.

Fires when someone schedules a meeting via Calendly. The standard hook for piping booked meetings into your CRM, sending prep, or auto-routing to the right team.

When new meeting booked in Calendly, create comment in GitHub.

Fires when someone schedules a meeting via Calendly. The standard hook for piping booked meetings into your CRM, sending prep, or auto-routing to the right team.

When new meeting booked in Calendly, create issue in GitHub.

Fires when someone schedules a meeting via Calendly. The standard hook for piping booked meetings into your CRM, sending prep, or auto-routing to the right team.

When new meeting booked in Calendly, create pull request in GitHub.

Fires when someone schedules a meeting via Calendly. The standard hook for piping booked meetings into your CRM, sending prep, or auto-routing to the right team.

How it works

Connect Calendly and GitHub in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Calendly and GitHub
Open Tiny Command, authorize Calendly and GitHub once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Calendly trigger
Drop the Calendly → Invitee Canceled trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/calendly.trigger-invitee-canceled
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the GitHub action
Drop the GitHub → Add Labels action below it. Map fields from the Calendly payload into the GitHub inputs.
github.add-labels-to-issue
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Calendly + GitHub.

When does Calendly + GitHub belong in a workflow?

For founder-led research interviews, dev-relations office hours, or design-partner calls where the conversation drives engineering work. The booking creates a GitHub issue to capture follow-ups, prep, or recordings.

How do I auto-create a GitHub issue from a research interview booking?

Calendly Invitee Created filtered to event_type = "user-research-interview" → GitHub Create Issue with the invitee name, company, scheduled time, and a prep template. Assign to the host.

Can I add post-meeting notes as a GitHub comment on the same issue?

Yes. After the meeting, fire a follow-up workflow (manual or scheduled) that pulls the meeting summary from Notion/Zoom recording → GitHub Add Comment on the linked issue. Standing record of customer signal.

How do I link a GitHub issue back to the original Calendly invite?

Include the Calendly event URI (canonical link) in the issue body. The reverse direction: store the GitHub issue URL in a Calendly hidden field if you're using a custom intake form.

Can I auto-label the GitHub issue by booking type?

Yes. Pass labels in Create Issue based on the Calendly event_type ("research-interview", "demo", "office-hours"). Labels must exist on the repo; create missing ones via a one-time provisioning workflow.

How do I avoid creating issues for cancelled meetings?

Use the Invitee Canceled trigger to close the linked GitHub issue. Or wait to create the issue at "meeting started" time via a delayed workflow rather than on booking creation.

Other apps that pair well with Calendly.

Calendly + Gmail

Calendly + Slack

Communication

Calendly + Google Sheets

Spreadsheets & Databases

Wire Calendly to GitHub in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo

Calendly + GitHub: turn user-research bookings into issue context.

Pick the way that fits your stack.

When something happens in Calendly, do it in GitHub.

Or fire it the other way around.

Common Calendly → GitHub workflows.

Connect Calendly and GitHub in five steps.

Questions about Calendly + GitHub.

Other apps that pair well with Calendly.

Wire Calendly to GitHub in 2 minutes.

Be the first to know what's next.