How to connect Chatwork and PagerDuty
Create a New Scenario to Connect Chatwork and PagerDuty
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 Chatwork, triggered by another scenario, or executed manually (for testing purposes). In most cases, Chatwork or PagerDuty will be your first step. To do this, click "Choose an app," find Chatwork or PagerDuty, and select the appropriate trigger to start the scenario.

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


Chatwork

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


Chatwork
⚙
PagerDuty

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

Chatwork
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Chatwork, PagerDuty, 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 Chatwork and PagerDuty integration works as expected. Depending on your setup, data should flow between Chatwork and PagerDuty (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Chatwork and PagerDuty
PagerDuty + Chatwork + Slack: When a new or updated incident occurs in PagerDuty, a message is sent to a dedicated Chatwork room. The on-call user is then notified in Slack via direct message.
PagerDuty + Jira + Chatwork: When a high-priority incident is acknowledged in PagerDuty, a linked incident ticket is created in Jira. The team is then notified about the new Jira ticket in a specified Chatwork room.
Chatwork and PagerDuty integration alternatives

About Chatwork
Use Chatwork with Latenode to automate team notifications and tasks. Send messages based on triggers from your CRM, database, or other apps. Latenode's visual builder simplifies creating complex workflows. Reduce manual updates, keep your team informed, and improve response times by integrating Chatwork into automated processes.
Similar apps
Related categories
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
See how Latenode works
FAQ Chatwork and PagerDuty
How can I connect my Chatwork account to PagerDuty using Latenode?
To connect your Chatwork account to PagerDuty on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Chatwork and click on "Connect".
- Authenticate your Chatwork and PagerDuty accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I escalate Chatwork messages to PagerDuty incidents?
Yes, you can! Latenode allows instant incident creation from Chatwork messages, triggering immediate alerts and ensuring critical issues are addressed promptly. Leverage low-code logic to filter important messages.
What types of tasks can I perform by integrating Chatwork with PagerDuty?
Integrating Chatwork with PagerDuty allows you to perform various tasks, including:
- Automatically create PagerDuty incidents from critical Chatwork messages.
- Send Chatwork notifications when a PagerDuty incident is acknowledged.
- Update Chatwork groups with PagerDuty incident resolution statuses.
- Trigger PagerDuty escalations based on Chatwork message content analysis via AI.
- Log Chatwork activity related to incidents for audit trails.
Can I customize Chatwork messages sent from PagerDuty within Latenode?
Yes, Latenode's visual editor and JavaScript code blocks let you fully customize Chatwork messages with dynamic data from PagerDuty incidents.
Are there any limitations to the Chatwork and PagerDuty integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex workflows with extremely high message volumes may require optimization.
- Custom JavaScript code requires technical expertise.
- Initial setup requires appropriate Chatwork and PagerDuty administrative privileges.