Per-pair page

Calendly + Jira: user-research bookings as issue context.

Create Jira issues for follow-up work from Calendly user-research interviews, design-partner calls, or sales-engineering sessions. Captures customer signal as engineering work.

Connect Jira and Calendly See reverse direction

Trigger app

Jira as the trigger

Workflows fire when something happens in Jira.

See all 6 triggers →

Action app

Calendly as the action

Workflows do something in Calendly, instantly.

Both directions

Pick the way that fits your stack.

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

Jira → Calendly

When something happens in Jira, do it in Calendly.

6 Jira triggers wired to 5 Calendly actions. Most-used pairing: Comment Created → Get Current User.

Calendly → Jira

Or fire it the other way around.

2 Calendly triggers wired to 17 Jira actions downstream.

See Calendly → Jira →

Popular pairings

Common Jira → Calendly workflows.

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

Showing 9 of 30 combinations

When comment created in Jira, get current user in Calendly.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, get event in Calendly.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, list event invitees in Calendly.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, list event types in Calendly.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When new issue in Jira, get current user in Calendly.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, get event in Calendly.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, list event invitees in Calendly.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, list event types in Calendly.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When issue deleted in Jira, get current user in Calendly.

Fires when an issue is deleted in Jira. Useful for audit/compliance logs and for tearing down related records in other systems.

How it works

Connect Jira and Calendly in five steps.

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

1
Connect
Authorize Jira and Calendly
Open Tiny Command, authorize Jira and Calendly once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Jira trigger
Drop the Jira → Comment Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/jira.trigger-comment-created
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 Calendly action
Drop the Calendly → Get Current User action below it. Map fields from the Jira payload into the Calendly inputs.
calendly.get-current-user
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 Jira + Calendly.

When is Calendly + Jira useful?

Whenever a meeting produces engineering follow-up — research-driven feature ideas, custom integration scoping, design-partner feedback. The booking creates a Jira issue to capture and track the work.

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

Calendly Invitee Created filtered to event_type = "user-research" → Jira Create Issue in your RESEARCH project, title = "Interview: {invitee_name}", body with company + scheduled time.

Can I link multiple Calendly bookings to the same Jira epic?

Yes. After Create Issue, call Update Issue with customfield_X = epic_key. All issues from this batch of interviews link to the same parent epic for rolled-up visibility.

How do I assign the Jira issue to the right engineer based on event type?

Switch on event_type to map to the right assignee (e.g., research interviews → product lead; design-partner calls → eng lead; SE sessions → solution engineer). Pass the assignee accountId at Create Issue.

Can I add a Jira comment with the post-meeting recap?

Yes. After the meeting, pull the Zoom recording → transcribe and summarize via AI → Jira Add Comment on the linked issue. Engineering captures customer signal as it actually surfaces.

How do I close the Jira issue if the Calendly meeting is cancelled?

Calendly Invitee Canceled → look up the linked Jira issue → Jira Transition Issue to "Cancelled" or "Closed-WontDo". Or delete the issue if the meeting was the only reason it existed.

Other apps that pair well with Jira.

Spreadsheets & Databases

Wire Jira to Calendly in 2 minutes.

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

Try for free Request a demo

Calendly + Jira: user-research bookings as issue context.

Pick the way that fits your stack.

When something happens in Jira, do it in Calendly.

Or fire it the other way around.

Common Jira → Calendly workflows.

Connect Jira and Calendly in five steps.

Questions about Jira + Calendly.

Other apps that pair well with Jira.

Wire Jira to Calendly in 2 minutes.

Be the first to know what's next.