How to connect PagerDuty and Pipefy
Create a New Scenario to Connect PagerDuty and Pipefy
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 Pipefy will be your first step. To do this, click "Choose an app," find PagerDuty or Pipefy, 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 Pipefy Node
Next, click the plus (+) icon on the PagerDuty node, select Pipefy from the list of available apps, and choose the action you need from the list of nodes within Pipefy.

PagerDuty
⚙

Pipefy

Authenticate Pipefy
Now, click the Pipefy node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Pipefy settings. Authentication allows you to use Pipefy through Latenode.
Configure the PagerDuty and Pipefy 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 Pipefy 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
⚙

Pipefy
Trigger on Webhook
⚙
PagerDuty
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring PagerDuty, Pipefy, 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 Pipefy integration works as expected. Depending on your setup, data should flow between PagerDuty and Pipefy (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 Pipefy
PagerDuty + Pipefy + Slack: When a new or updated high-priority incident is created in PagerDuty, a card is automatically created in Pipefy to track its resolution. A notification is then sent to a dedicated Slack channel to alert the relevant team.
Pipefy + PagerDuty + Microsoft Teams: When a card in Pipefy reaches a critical stage (e.g., "Blocked" or "Awaiting Approval"), an incident is created in PagerDuty to ensure prompt attention. Simultaneously, an alert is posted in a Microsoft Teams channel to keep stakeholders informed of the issue.
PagerDuty and Pipefy 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 Pipefy
Orchestrate Pipefy process management inside Latenode for end-to-end automation. Trigger flows on card changes, create new cards from external data, and sync Pipefy data with other apps. Bypass manual updates and build complex workflows using visual tools, code, or AI — without step limits or vendor lock-in.
Related categories
See how Latenode works
FAQ PagerDuty and Pipefy
How can I connect my PagerDuty account to Pipefy using Latenode?
To connect your PagerDuty account to Pipefy 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 Pipefy accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I escalate Pipefy cards based on PagerDuty incidents?
Yes, you can! With Latenode, automatically escalate Pipefy cards when a PagerDuty incident is triggered, ensuring critical issues receive immediate attention. Customize the escalation logic using low-code blocks.
What types of tasks can I perform by integrating PagerDuty with Pipefy?
Integrating PagerDuty with Pipefy allows you to perform various tasks, including:
- Automatically creating Pipefy cards from new PagerDuty incidents.
- Updating Pipefy cards when PagerDuty incidents are resolved.
- Triggering PagerDuty incidents from specific Pipefy card stages.
- Syncing incident status updates between PagerDuty and Pipefy.
- Sending custom notifications based on integrated PagerDuty/Pipefy data.
How do I map custom fields between PagerDuty and Pipefy in Latenode?
Latenode’s visual editor allows you to easily map custom fields. Use the data mapping feature in the integration settings to sync specific data points between PagerDuty and Pipefy.
Are there any limitations to the PagerDuty and Pipefy integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Initial data synchronization may require manual setup.
- Complex conditional logic might necessitate JavaScript coding.
- Rate limits of PagerDuty and Pipefy APIs apply to all integrations.