Routines overview
What routines are, how the Routines page is laid out, and where to install, review runs, work alerts and build your own.
A routine is a scheduled health check that watches your workspace and tells you when something needs fixing: a marketplace report that hasn't been imported, links without an affiliate tag, a price drop on a product you link to, a Creator Connect application waiting too long for review. Each time a routine runs it records what it checked, and when it finds a problem it opens an alert that names the affected links, tags, campaigns or applications.
Routines are different from Automations. Routines watch for problems and keep them visible until they're fixed. Automations do work for you when something happens, such as posting a deal or sending a message.
Before you start
- Routines are part of your plan. If your plan doesn't include them, the Routines page shows an Upgrade card.
- Your role needs access to Routines. Viewing, installing, running and editing are separate permissions, so a teammate may see routines but not install or run them.
- Building your own routines (custom routines) is a separate plan feature. See Build a custom routine.
The Routines page
Open Routines in the sidebar.
At the top, five counts summarize every installed routine:
- Healthy: the last check found nothing wrong.
- Needs Attention: routines in warning or critical health.
- Critical: routines with a critical problem.
- Overdue: routines whose next scheduled run is in the past.
- Runs Today: routines that ran today.
Below them are four tabs:
- Overview: the Priority queue (up to six routines in warning or critical health), shortcuts to required system routines and recommended templates you haven't installed, and Recent resolutions, a short log of alerts that were resolved.
- Installed: every installed routine with its health, alert count and last run.
- Alerts: open alerts across all routines. See Work routine alerts.
- Catalog: templates you can install. See Install a routine from the catalog.
The header has System routines (the routines Pointerly manages), My routines and New custom routine when your plan includes custom routines.
How a routine works
Each routine has a schedule (every few hours, daily at a set time, or weekly on a set day), a set of thresholds that decide when something counts as a problem, and outputs that decide how you hear about it:
- Operational issue: an alert that stays open in Routines until the condition clears.
- In-app notification: a notification in Pointerly when an alert opens or escalates.
- Email: critical issues email right away; warnings that stay unresolved email later.
- Operations board: a card on the Operations board, when Pipeline is available for your team.
- Automation event: lets an automation react to the alert, for example to post it to Slack.
When the condition clears on a later run, the alert resolves on its own.
Routine health
Every installed routine shows a health badge:
- Healthy: the last run found nothing to fix.
- Warning: something needs attention but isn't urgent yet.
- Critical: something is broken now, such as a report that is long overdue.
- Unknown: the routine hasn't run yet.
Common tasks
- Install a routine from the catalog and tune its thresholds and outputs.
- Review routine runs and see exactly which links or tags a run flagged.
- Work routine alerts: mark them seen, open the fix, resolve them.
- System routines: the routines Pointerly manages and which ones are always on.
- Build a custom routine on the canvas.