How to connect PagerDuty and Awork
Create a New Scenario to Connect PagerDuty and Awork
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a PagerDuty, triggered by another scenario, or executed manually (for testing purposes). In most cases, PagerDuty or Awork will be your first step. To do this, click "Choose an app," find PagerDuty or Awork, and select the appropriate trigger to start the scenario.

Add the PagerDuty Node
Select the PagerDuty node from the app selection panel on the right.

PagerDuty
Configure the PagerDuty
Click on the PagerDuty node to configure it. You can modify the PagerDuty URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Awork Node
Next, click the plus (+) icon on the PagerDuty node, select Awork from the list of available apps, and choose the action you need from the list of nodes within Awork.

PagerDuty
⚙
Awork
Authenticate Awork
Now, click the Awork node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Awork settings. Authentication allows you to use Awork through Latenode.
Configure the PagerDuty and Awork Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the PagerDuty and Awork Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Awork
Trigger on Webhook
⚙
PagerDuty
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring PagerDuty, Awork, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the PagerDuty and Awork integration works as expected. Depending on your setup, data should flow between PagerDuty and Awork (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect PagerDuty and Awork
PagerDuty + Awork + Slack: When a new or updated incident is created in PagerDuty, a task is created in Awork to address the incident. A notification is then sent to a dedicated Slack channel to inform the team.
Awork + PagerDuty + Microsoft Teams: When a task in Awork is updated, specifically if it's marked as blocked, a high-priority incident is triggered in PagerDuty and the team is notified in Microsoft Teams via a channel message.
PagerDuty and Awork integration alternatives
About PagerDuty
Integrate PagerDuty alerts into Latenode to automate incident response. Create flows that trigger actions based on alert severity, like escalating to specific channels or running diagnostic scripts. Centralize incident data and automate follow-ups. Using Latenode gives you a customizable, scalable response system without complex coding.
Similar apps
Related categories
About Awork
Manage Awork tasks in Latenode to automate project updates and reporting. Trigger flows on new tasks, sync deadlines across tools, or create custom reports. Use Latenode's logic functions and webhooks to connect Awork to any system, crafting automated workflows without complex coding, and scale project management tasks efficiently.
Related categories
See how Latenode works
FAQ PagerDuty and Awork
How can I connect my PagerDuty account to Awork using Latenode?
To connect your PagerDuty account to Awork on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select PagerDuty and click on "Connect".
- Authenticate your PagerDuty and Awork accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Awork tasks from PagerDuty incidents?
Yes, you can! Latenode lets you build this automation visually, even adding custom logic with JavaScript for advanced routing. This keeps Awork updated as incidents are resolved.
What types of tasks can I perform by integrating PagerDuty with Awork?
Integrating PagerDuty with Awork allows you to perform various tasks, including:
- Automatically creating new Awork tasks when PagerDuty incidents are triggered.
- Updating Awork task statuses based on PagerDuty incident resolution.
- Sending Awork notifications when new PagerDuty incidents are assigned.
- Adding PagerDuty incident details to Awork task descriptions.
- Closing Awork tasks automatically when corresponding PagerDuty incidents resolve.
Can I customize incident routing from PagerDuty in Latenode workflows?
Yes, Latenode’s visual editor enables highly customized routing. Use JavaScript blocks to filter and route incidents based on severity.
Are there any limitations to the PagerDuty and Awork integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Real-time data synchronization depends on the API limits of PagerDuty and Awork.
- Complex data transformations might require custom JavaScript code in Latenode.
- Historical data migration between PagerDuty and Awork is not directly supported.