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

PagerDuty
β

SendPulse

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

SendPulse
Trigger on Webhook
β
PagerDuty
β
β
Iterator
β
Webhook response

Save and Activate the Scenario
After configuring PagerDuty, SendPulse, 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 SendPulse integration works as expected. Depending on your setup, data should flow between PagerDuty and SendPulse (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 SendPulse
PagerDuty + SendPulse + Slack: When a high-priority incident is declared in PagerDuty, an SMS message is sent via SendPulse to the on-call team. Simultaneously, a notification is posted to a designated Slack channel to inform all relevant teams about the incident.
SendPulse + PagerDuty + Google Sheets: This automation tracks the performance of SendPulse campaigns. When conversion rates drop below a predefined threshold, a PagerDuty incident is triggered to alert the responsible team. The campaign performance data is continuously logged in a Google Sheet for analysis.
PagerDuty and SendPulse 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 SendPulse
Use SendPulse in Latenode for automated email & SMS marketing. Trigger campaigns based on real-time events, segment contacts dynamically, and personalize messages using data from any app. Automate list cleaning and optimize send times in response to user behavior. Connect SendPulse to any data source for smarter, event-driven communication workflows.
Related categories
See how Latenode works
FAQ PagerDuty and SendPulse
How can I connect my PagerDuty account to SendPulse using Latenode?
To connect your PagerDuty account to SendPulse 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 SendPulse accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I notify users of PagerDuty incidents via SMS?
Yes, easily! Latenode's visual editor simplifies setup. SendPulse delivers instant SMS alerts for critical PagerDuty incidents, ensuring faster response times.
What types of tasks can I perform by integrating PagerDuty with SendPulse?
Integrating PagerDuty with SendPulse allows you to perform various tasks, including:
- Send SMS alerts via SendPulse for high-priority PagerDuty incidents.
- Create or update SendPulse contacts when PagerDuty incidents are resolved.
- Send email notifications via SendPulse when a new PagerDuty incident is created.
- Automatically unsubscribe contacts in SendPulse if they acknowledge an incident in PagerDuty.
- Log PagerDuty incident details in a SendPulse mailing list for reporting.
Can I customize alert messages sent from PagerDuty within Latenode?
Yes! Latenode lets you use JavaScript to fully customize messages from PagerDuty to SendPulse, creating highly personalized alerts.
Are there any limitations to the PagerDuty and SendPulse integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits from PagerDuty and SendPulse APIs may affect high-volume workflows.
- Complex data transformations may require JavaScript knowledge.
- Historical data migration between the services isn't directly supported.