STEP 1
Connect CircleCI and PagerDuty
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
CircleCI and PagerDuty Integration
Keep CircleCI and PagerDuty in sync by integrating their events and actions. When developer tools events happen in CircleCI, update the PagerDuty automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about CircleCI and PagerDuty
Detailed info you need to know about CircleCI and PagerDuty integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect CircleCI to PagerDuty
Set up your CircleCI and PagerDuty integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected CircleCI and PagerDuty nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between CircleCI and PagerDuty. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between CircleCI and PagerDuty work in WEXTL?
WEXTL exposes actions and triggers for CircleCI and PagerDuty that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
CircleCI triggersPagerDuty actions
CircleCI modules
- Watch Workflow & Job EventsTriggers when a workflow or job completes in CircleCI.
- Add Environment VariableCreates environment variable.
- Cancel Job by IDCancels job by id.
- Cancel Job by NumberCancels job by number.
- Cancel WorkflowCancels workflow.
- Continue PipelineContinues pipeline.
- Create Checkout KeyCreates checkout key.
- Create ContextCreates context.
- Create EnvvarCreates envvar.
- Create GroupCreates group.
- Create OrganizationCreates organization.
- Create OTLP ExporterCreates otlp exporter.
- Create Pipeline DefinitionCreates pipeline definition.
- Create Policy BundleCreates policy bundle.
- Create Project in OrgCreates project in org.
- Create RestrictionCreates restriction.
- Create ScheduleCreates schedule.
- Create TriggerCreates trigger.
- Create URL Orb Allow-list EntryCreates url orb allow-list entry.
- Create Usage ExportCreates usage export.
- Create WebhookManually creates an outbound webhook subscription in CircleCI. For the platform's own trigger lifecycle (auto-managed attach/detach), use the Watch Workflow & Job Events trigger instead — using both for the same URL double-subscribes it.
- Delete Checkout KeyDeletes checkout key.
- Delete ContextDeletes context.
- Delete Environment VariableDeletes environment variable.
- Delete EnvvarDeletes envvar.
- Delete GroupDeletes group.
- Delete Org OIDC ClaimsDeletes org oidc claims.
- Delete OrganizationDeletes organization.
- Delete OTLP ExporterDeletes otlp exporter.
- Delete Pipeline DefinitionDeletes pipeline definition.
- Delete ProjectDeletes project.
- Delete Project OIDC ClaimsDeletes project oidc claims.
- Delete RestrictionDeletes restriction.
- Delete ScheduleDeletes schedule.
- Delete TriggerDeletes trigger.
- Delete URL Orb Allow-list EntryDeletes url orb allow-list entry.
- Delete WebhookManually deletes an outbound webhook subscription in CircleCI. Do not use this to remove a Watch Workflow & Job Events trigger's own subscription — removing/deactivating that trigger node detaches it automatically; deleting its webhook here directly leaves the trigger node pointing at a subscription CircleCI no longer has.
- Get Checkout KeyReturns checkout key.
- Get ComponentReturns component.
- Get ContextReturns context.
- Get Context RestrictionsReturns context restrictions.
- Get Current UserReturns current user.
- Get Decision Audit LogsReturns decision audit logs.
- Get Decision by IDReturns decision by id.
- Get Decision SettingsReturns decision settings.
- Get EnvironmentReturns environment.
- Get EnvvarReturns envvar.
- Get GroupReturns group.
- Get JobReturns job.
- Get My PipelinesReturns my pipelines.
PagerDuty modules
- Add a User to a TeamAdds a user to a team.
- Add an Escalation Policy to a TeamAdds an escalation policy to a team.
- Add Notification SubscribersAdds notification subscribers to an incident status update.
- Assign TagsAssigns tags to a supported entity.
- Cancel Responder Requests for an IncidentCancels pending responder requests on an incident.
- Convert a Service's Event Rules into Event Orchestration RulesConverts a service's event rules into event orchestration rules.
- Create a Change EventCreates a new change event.
- Create a Maintenance WindowCreates a new maintenance window.
- Create a New IntegrationCreates a new integration on a service.
- Create a Note on an IncidentCreates a new note on an incident.
- Create a Responder Request for an IncidentCreates a new responder request for an incident.
- Create a ScheduleCreates a new schedule.
- Create a ServiceCreates a new service.
- Create a Status Update on an IncidentCreates a new status update on an incident.
- Create a TagCreates a new tag.
- Create a TeamCreates a new team.
- Create a UserCreates a new user.
- Create a User Contact MethodCreates a new user contact method.
- Create a User Handoff Notification RuleCreates a new user handoff notification rule.
- Create a User Notification RuleCreates a new user notification rule.
- Create a User Status Update Notification RuleCreates a new user status update notification rule.
- Create an Escalation PolicyCreates a new escalation policy.
- Create an Event Rule on a ServiceCreates a new event rule on a service.
- Create an IncidentCreates a new incident.
- Create Notification SubscriptionsCreates a new notification subcriptions.
- Create One or More OverridesCreates one or more schedule overrides.
- Create Team Notification SubscriptionsCreates a new team notification subscriptions.
- Delete a Note on an IncidentRemoves an existing note on an incident.
- Delete a ScheduleRemoves an existing schedule.
- Delete a ServiceRemoves an existing service.
- Delete a TagRemoves an existing tag.
- Delete a TeamRemoves an existing team.
- Delete a UserRemoves an existing user.
- Delete a User's Contact MethodRemoves an existing user's contact method.
- Delete a User's Handoff Notification RuleRemoves an existing user's handoff notification rule.
- Delete a User's Notification RuleRemoves an existing user's notification rule.
- Delete a User's SessionRemoves an existing user's session.
- Delete a User's Status Update Notification RuleRemoves an existing user's status update notification rule.
- Delete All User SessionsDeletes all active sessions for a user.
- Delete an Escalation PolicyRemoves an existing escalation policy.
- Delete an Event Rule from a ServiceRemoves an existing event rule from a service.
- Delete an OverrideRemoves an existing override.
- Delete or End a Maintenance WindowRemoves an existing or end a maintenance window.
- Enable a Webhook SubscriptionRe-enables a disabled webhook subscription.
- Get a Change EventReturns a single change event.
- Get a Log EntryReturns a single log entry.
- Get a Maintenance WindowReturns a single maintenance window.
- Get a ScheduleReturns a single schedule.
- Get a ServiceReturns a single service.
- Get a TagReturns a single tag.
Frequently asked questions
Common questions about connecting CircleCI and PagerDuty.
Connect your CircleCI and PagerDuty accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when CircleCI's "Watch Workflow & Job Events" fires, WEXTL can "Add a User to a Team" in PagerDuty. CircleCI has 1 trigger (including Watch Workflow & Job Events); PagerDuty has 148 actions (including Add a User to a Team, Add an Escalation Policy to a Team, and Add Notification Subscribers). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. CircleCI-to-PagerDuty automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment CircleCI (or PagerDuty) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your CircleCI + PagerDuty automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the CircleCI and PagerDuty integration.
- CircleCI and PagerDuty integration source code, module specs and credentials implementation.
- Our CircleCI and PagerDuty integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for CircleCI and PagerDuty — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- CircleCI integration information
- PagerDuty integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library