Turn cron runs into an automation schedule pin
Show when jobs run, last/next execution, and status—PATCH from n8n so operators trust the live schedule on the board.
Cron jobs are invisible until they fail. An automation schedule pin displays cadence, last run, next run, and status—updated by your pipeline so the canvas is the ops calendar.
Example: automation schedule pin
Loading schedule...
Why use a automation schedule pin?
Trust at a glance
See if the nightly sync actually ran.
Single ops surface
Schedules sit beside KPIs and runbooks.
API-updated
n8n PATCHes the pin after each execution.
Getting started
Add an automation schedule pin per critical job or one pin with multiple rows. After each n8n run, PATCH last_run and status fields. Pair with trace pins for failure detail.
Frequently Asked Questions (FAQ)
How many schedules per pin?
Use one row per job or split across pins by team—keep labels obvious.
What statuses should we use?
Common: success, running, failed, skipped—match what your monitor emits.
Schedule pin vs calendar pin?
Calendar = human events and releases. Automation schedule = machine job cadence.