Capture alert context as an incident wraps up
Bring the relevant Pingdom alert actions into the incident closeout while details are still fresh, then plan any remaining work in Clockify.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Pingdom Alert Actions
Tool to retrieve a list of alert actions for your pingdom account. use when you need to fetch actions with optional filters: pagination, check ids, user ids, status, via channel, or time range.
Why this helps
Incident context fades quickly after resolution, making it harder to remember the alerts and follow-up that mattered.
- Gather alert history at the moment an incident is closed.
- Reduce effort reconstructing operational context later.
- Make remaining reliability work easier to carry into Clockify.
Setup
Build it in a few focused steps.
- 1Connect Clockify and Pingdom to Notis once through the portal.
- 2Create a Notis webhook automation and point your incident tracker’s close signal to its endpoint.
- 3In one prompt, ask Notis to retrieve the relevant Pingdom alert actions and summarize potential follow-up.
- 4Choose the incoming webhook trigger and your reporting channel.
- 5Test with a real incident close event and confirm the summary has useful context.
Questions about this workflow
Does this resolve Pingdom alerts?
No. It retrieves alert action records when your incident system signals closure.
Can the webhook include an incident identifier?
Your external system can include context in its request; describe in the prompt how Notis should use the available context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clockify to Pingdom. A trigger fires from one place; an action lands in another.
Clockify triggers
Pingdom actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Pingdom Alert Actions
Tool to retrieve a list of alert actions for your pingdom account. use when you need to fetch actions with optional filters: pagination, check ids, user ids, status, via channel, or time range.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Checks List
Tool to retrieve an overview list of all uptime checks with optional filters and pagination. use when you need to fetch checks after configuring probes or tags.
Get Contact Details
Tool to fetch detailed info of a specific pingdom alerting contact. use when you need full configuration of a contact’s notification methods by contact id.
Get Contacts
Tool to retrieve all alerting contacts. use when you need to list every contact along with their notification targets after establishing a pingdom session.
Get Credits
Tool to retrieve account credit and rate-limit information. use when you need to check remaining checks and api credits before proceeding with further requests.
List Maintenance Occurrences
Tool to list maintenance occurrences. use when you need occurrences filtered by time range or a specific maintenance window id.
Get Maintenance Windows
Tool to retrieve a list of maintenance windows. use when you need to list user's maintenance windows with optional pagination and time range filters.
Get Probes
Tool to retrieve all pingdom probe servers. use when you need to list available probes for uptime or transaction checks.
Connect any two apps with Notis in the middle.
Clockify and Pingdom, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Pingdom.