Catch address validation outages before deliveries are affected
When your Addresszen integration reports that address checks are unavailable, create a Better Stack incident so the right person can investigate.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Incident
Creates an incident and alerts the on-call responder through the applicable escalation policy.
Why this helps
A broken address check can quietly disrupt checkout and shipping while the team is focused elsewhere.
- Create an incident from an Addresszen availability signal.
- Bring the service disruption into your existing on-call workflow.
- Reduce the chance that address failures go unnoticed.
Setup
Build it in a few focused steps.
- 1Connect Addresszen and Better Stack once in the Notis portal.
- 2Create an automation by telling Notis to open a Better Stack incident when an Addresszen outage signal arrives.
- 3Pick the Notis webhook trigger and send the signal to its HTTP endpoint from your existing integration or service.
- 4Choose where Notis should send run reports.
- 5Test with one real outage signal and review the incident details.
Questions about this workflow
Does Addresszen provide a trigger event for this workflow?
No Addresszen trigger event is listed. This workflow starts when an HTTP request reaches the Notis webhook, so your existing service must send the outage signal.
What happens when the webhook receives an outage signal?
Notis asks Better Stack to create an incident, which alerts the on-call person according to the selected escalation policy or default team settings.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addresszen to Better stack. A trigger fires from one place; an action lands in another.
Addresszen triggers
Better stack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Escalation Policy
Creates an incident escalation policy that defines who is notified and when.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Acknowledge Incident
Acknowledges an active incident, stopping further escalations.
Create Heartbeat Group
Creates a group to organize related heartbeat checks.
Create Outgoing Webhook Integration
Creates an integration to send event notifications to an endpoint.
Create Heartbeat
Creates a heartbeat monitor that checks for regular signals from a service.
Create Source Group
Creates a group to organize related log sources.
Delete Escalation Policy
Permanently deletes an escalation policy.
Create Incident
Creates an incident and alerts the on-call responder through the applicable escalation policy.
Connect any two apps with Notis in the middle.
Addresszen and Better stack, 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 Better stack.