STEP 1
Connect Currents 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.
Currents and PagerDuty Integration
Build developer tools workflows between Currents and PagerDuty on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Currents and PagerDuty
Detailed info you need to know about Currents and PagerDuty integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Currents to PagerDuty
Set up your Currents and PagerDuty integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Currents 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 Currents and PagerDuty. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Currents and PagerDuty work in WEXTL?
WEXTL exposes actions and triggers for Currents 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.
Currents triggersPagerDuty actions
Currents modules
- Cancel RunCancels a run that is still in progress.
- Cancel Run by GitHub CICancels a run identified by its GitHub Actions workflow run.
- Create ActionCreates a new action that quarantines, skips, or tags matching tests.
- Create Jira IssueCreates a Jira issue from a test in a run and links it back.
- Delete ActionArchives an action so it stops applying to tests.
- Delete Project TermDeletes a tag term from a project's filter list.
- Delete RunDeletes a run and all of its associated data.
- Disable ActionDisables an action without archiving it.
- Enable ActionEnables an action that is currently disabled.
- Find RunReturns the most recent completed run matching the criteria.
- Generate Test SignatureComputes the stable signature for a test from its project, spec file, and title.
- Get ActionReturns a single action by its identifier.
- Get Affected Test ExecutionsRetrieves the executions of one affected test in a date range.
- Get InstanceReturns a single spec-file instance with its test results.
- Get ProjectReturns a single project by its identifier.
- Get Project InsightsReturns aggregated run and test metrics for a project.
- Get RunReturns a single run with its groups and spec results.
- Get Test Failure ContextReturns structured failure context for a run, a spec file, or a single test.
- Get Test ResultsRetrieves the historical executions of one test signature.
- Get WebhookReturns a single webhook by its identifier.
- Link Jira IssueLinks an existing Jira issue to a test in a run.
- List Action Test ExecutionsRetrieves the test executions where one action was applied.
- List ActionsRetrieves the actions configured for a project.
- List Affected TestsRetrieves the tests affected by actions in a date range.
- List ErrorsRetrieves errors from the Errors Explorer for a project.
- List Jira Issue TypesRetrieves the Jira issue types available for a Jira project.
- List Jira ProjectsRetrieves the Jira projects available to the connected Jira integration.
- List Project RunsRetrieves the test runs recorded for a project.
- List Project TermsRetrieves the filter terms of one kind recorded for a project.
- List ProjectsRetrieves the projects in your Currents organization.
- List Pull RequestsRetrieves the pull requests with run activity for a project.
- List Spec FilesRetrieves spec files from the Spec Files Explorer for a project.
- List TestsRetrieves tests from the Tests Explorer for a project.
- List WebhooksRetrieves the webhooks configured for a project.
- Make an API CallPerforms an arbitrary authorized API call.
- Reset RunResets failed spec files in a run so they can run again.
- Update ActionUpdates an existing action.
- Update WebhookUpdates the URL, events, headers, or label of a webhook.
- Watch EventsTriggers when a test run starts, finishes, times out, or is cancelled.
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 Currents and PagerDuty.
Connect your Currents 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 Currents's "Watch Events" fires, WEXTL can "Add a User to a Team" in PagerDuty. Currents has 1 trigger (including Watch 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. Currents-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 Currents (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 Currents + 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 Currents and PagerDuty integration.
- Currents and PagerDuty integration source code, module specs and credentials implementation.
- Our Currents and PagerDuty integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Currents 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.
- Currents integration information
- PagerDuty integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library