Connect PagerDuty to Calendly with an AI agent
An agent watches incidents and on-call state in PagerDuty, decides what matters, and updates an event type in Calendly. Velaris connects PagerDuty and Calendly through its capability mesh, so you describe the outcome instead of drawing a trigger-and-action flowchart — and anything outbound or irreversible waits for your approval.
PagerDuty is on the roadmap — join the list to get it first.
What you can automate
- Velaris can read incidents and on-call schedules in PagerDuty, judge what's worth acting on, and updates an event type in Calendly — so the time is blocked before the day fills up.
- When incidents in PagerDuty need something done in Calendly, the agent does it and stops for your approval on anything outbound or irreversible.
- On a schedule or on a trigger, it can pull invitee intake answers in Calendly from what it found in PagerDuty — every write logged, scoped and reversible.
How it works
- 1
Connect PagerDuty and Calendly
Authorize both tools with scoped access you control.
- 2
Say what you want
Describe the outcome in a sentence — no trigger/action graph to draw.
- 3
Set the approval tier
Reads run automatically; outbound or irreversible steps wait for your tap.
Common questions
Can Velaris connect PagerDuty to Calendly without code?
Yes. Connect both tools, then describe the outcome in plain language — the agent selects the right actions from the capability mesh itself. There's no flowchart to build.
How is this different from a PagerDuty-to-Calendly Zap or automation?
A rule fires the same way every time. An agent reads the PagerDuty context, decides whether it matters, and adapts what it does in Calendly — pausing for approval on anything outbound or irreversible.
Will it act in Calendly without asking me?
Only for read-only steps. Writes are logged, and anything destructive or outbound needs an explicit human approval — credentials are scoped to the run and expire with it.