Announce resolution
When an incident is resolved in Pingdom, post an all-clear message in Chatwork.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Pingdom Explore Pingdom →
TriggersFires when a monitor or check in Pingdom raises an alert.
Fires when an incident is opened or updated in Pingdom.
Fires when a monitored site, service or alarm in Pingdom changes state.
Opens a new incident or alert in Pingdom.
Acknowledges an open incident in Pingdom.
Resolves an incident in Pingdom.
Chatwork Explore Chatwork →
TriggersFires when a new message is posted to a channel in Chatwork.
Fires when your team or a keyword is mentioned in Chatwork.
Fires when a new channel is created in Chatwork.
Fires when a new file is shared in Chatwork.
Posts a message to a channel in Chatwork.
Sends a direct message to a person in Chatwork.
Creates a new channel in Chatwork.
Adds a user to a channel in Chatwork.
More Pingdom + Chatwork workflows
See all Pingdom + Chatwork integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Announce resolution” between Pingdom and Chatwork?
Yes — describe it in the box above and Knit's Integrations Agent researches Pingdom and Chatwork's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why post monitoring alerts to team chat?
Engineers already work in Chatwork. Posting Pingdom alerts there means problems are seen quickly and the discussion happens alongside the alert.
Can I route alerts to different channels?
Yes. Send alerts from Pingdom to different Chatwork channels based on the service, monitor or severity.