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.
Workflows fire when something happens in GitHub.
- New GitHub EventWebhook
Workflows do something in Calendly, instantly.
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in GitHub, do it in Calendly.
1 GitHub triggers wired to 5 Calendly actions. Most-used pairing: New GitHub Event → Get Current User.
Or fire it the other way around.
2 Calendly triggers wired to 23 GitHub actions downstream.
See Calendly → GitHub →Common GitHub → Calendly workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when the selected events occur on a GitHub repository. One webhook is registered per workflow on the chosen repo, with the events list filtered server-side by GitHub. Pick from push, pull_request, issues, release, deployment, and many others.
Fires when the selected events occur on a GitHub repository. One webhook is registered per workflow on the chosen repo, with the events list filtered server-side by GitHub. Pick from push, pull_request, issues, release, deployment, and many others.
Fires when the selected events occur on a GitHub repository. One webhook is registered per workflow on the chosen repo, with the events list filtered server-side by GitHub. Pick from push, pull_request, issues, release, deployment, and many others.
Fires when the selected events occur on a GitHub repository. One webhook is registered per workflow on the chosen repo, with the events list filtered server-side by GitHub. Pick from push, pull_request, issues, release, deployment, and many others.
Connect GitHub and Calendly in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize GitHub and Calendly
Open Tiny Command, authorize GitHub and Calendly once each. Both connections are available to every workflow on your account.
- 2TriggerPick a GitHub trigger
Drop the GitHub → New GitHub Event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/github.trigger-event - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Calendly action
Drop the Calendly → Get Current User action below it. Map fields from the GitHub payload into the Calendly inputs.
calendly.get-current-user - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about GitHub + Calendly.
When does Calendly + GitHub belong in a workflow?
How do I auto-create a GitHub issue from a research interview booking?
Can I add post-meeting notes as a GitHub comment on the same issue?
How do I link a GitHub issue back to the original Calendly invite?
Can I auto-label the GitHub issue by booking type?
How do I avoid creating issues for cancelled meetings?
Other apps that pair well with GitHub.
Wire GitHub to Calendly in 2 minutes.
Free tier available. No credit card. No onboarding call.
