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

PagerDuty
⚙

ClickSend

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

ClickSend
Trigger on Webhook
⚙
PagerDuty
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring PagerDuty, ClickSend, 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 ClickSend integration works as expected. Depending on your setup, data should flow between PagerDuty and ClickSend (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 ClickSend
PagerDuty + ClickSend + Slack: When a new or updated incident occurs in PagerDuty, send an SMS message via ClickSend to the on-call user, then notify a specified Slack channel about the incident.
ClickSend + PagerDuty + Email: When a new SMS message is received via ClickSend, trigger a new incident in PagerDuty, then send a confirmation email using SMTP.
PagerDuty and ClickSend 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 ClickSend
Use ClickSend in Latenode to automate SMS, email, or voice messaging. Build workflows that trigger messages based on events in your other apps. Improve customer engagement by automating personalized notifications. Latenode’s visual editor simplifies integration and scales your outreach without extra code or per-step costs.
Related categories
See how Latenode works
FAQ PagerDuty and ClickSend
How can I connect my PagerDuty account to ClickSend using Latenode?
To connect your PagerDuty account to ClickSend 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 ClickSend accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I send SMS alerts for critical PagerDuty incidents?
Yes, you can! Latenode lets you trigger ClickSend SMS messages when high-priority incidents occur in PagerDuty, ensuring rapid response and minimizing downtime. Customize messages using data from PagerDuty.
What types of tasks can I perform by integrating PagerDuty with ClickSend?
Integrating PagerDuty with ClickSend allows you to perform various tasks, including:
- Automatically send SMS notifications to on-call personnel for new PagerDuty incidents.
- Create ClickSend contacts from PagerDuty users to streamline communication.
- Escalate urgent PagerDuty incidents via ClickSend voice calls if not acknowledged.
- Log PagerDuty incident details in ClickSend custom fields for reporting.
- Send follow-up SMS surveys via ClickSend after incident resolution in PagerDuty.
Can Latenode handle custom PagerDuty event payloads?
Yes. Latenode supports parsing and using custom PagerDuty event data, enabling highly tailored ClickSend messages and workflows beyond standard alerts.
Are there any limitations to the PagerDuty and ClickSend integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex logic requires some JavaScript knowledge for advanced customization.
- High ClickSend SMS volumes may incur additional costs based on ClickSend's pricing.
- PagerDuty API rate limits may affect the speed of real-time data synchronization.