Introduction
What Anchor does and how its notification lifecycle works.
Anchor turns automations into persistent notifications that remain actionable until the required outcome is recorded.
The core workflow
- Complete onboarding and optionally explore Anchor with paused Automation drafts.
- Connect a Pushover application token and user key when you are ready to enable delivery.
- Create and activate a scheduled Automation, or let another system create a Notification directly.
- Anchor creates and delivers a notification.
- Acknowledge, complete, snooze, skip, or cancel the notification as allowed by the automation.
- Anchor keeps automation-created history until you delete its automation and
direct API history until you delete your account.
Response requirements
- Inform sends once and succeeds when Pushover accepts the message.
- Acknowledge continues according to the automation policy until you acknowledge it.
- Complete distinguishes seeing the notification from finishing the work.
Start with Getting started, or open the API guide to automate Anchor.