Scheduled detection half of the Vercel to Statuspage incident loop. It reads recent failed production Vercel deployments, writes one data.shared proposal for the first unhandled deployment, and notifies the owner to review whether customer communication is needed. It never creates or updates Statuspage incidents, rolls back deployments, promotes deployments, pauses projects, mutates domains or environment variables, or calls arbitrary APIs. Vercel native notifications and rollback controls own their native surfaces; this recipe only creates a Recued-visible cross-system proposal that an owner can approve or dismiss with create-approved-statuspage-incident-from-vercel.
Propose Statuspage review for failed Vercel deployment
Scheduled detection half of the Vercel to Statuspage incident loop. It reads recent failed production Vercel deployments, writes one data.shared proposal for the first unhandled deployment, and notifies the owner to review whether customer communication is needed. It never creates or updates Statuspage incidents, rolls back deployments, promotes deployments, pauses projects, mutates domains or environment variables, or calls arbitrary APIs. Vercel native notifications and rollback controls own their native surfaces; this recipe only creates a Recued-visible cross-system proposal that an owner can approve or dismiss with create-approved-statuspage-incident-from-vercel.
Complete workflow
Deployment Incident Loop - Vercel + Statuspage
2 pinned recipes
Workflow pack that closes the loop between Vercel production deployment failures and owner-reviewed Statuspage incident communication. It depends on the Vercel and Statuspage capability packs, detects one unhandled failed production deployment at a time, writes a data.shared proposal, notifies the owner, and provides a manual action recipe that either creates the Statuspage incident and links it back to the Vercel deployment or dismisses the proposal when no customer-facing incident is needed. It does not duplicate Vercel's native deployment notifications, rollback controls, or webhooks; those stay in Vercel. It also does not auto-publish customer-facing Statuspage updates from unattended automation.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Owner-invoked action half of the Vercel to Statuspage incident loop. It reads one awaiting_owner_approval proposal written by vercel-statuspage-incident-proposal, then either creates exactly one Statuspage incident from deterministic proposal copy or dismisses the proposal as no customer impact. Running this recipe is the owner's approval or decline. It takes no outward-facing action when there is no pending proposal or required Statuspage incident copy is missing.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Data fetch
existing_proposals
?
▼
Process (39 steps)
existing_proposals_family
filter
Filter by condition
resolved_team_id
trim
Trim whitespace from setting team id
resolved_team_slug
trim
Trim whitespace from setting team slug
resolved_project_id
trim
Trim whitespace from setting project id
page_id
trim
Trim whitespace from setting statuspage page id
incident_name_override_text
trim
Trim whitespace from setting incident name override
incident_body_override_text
trim
Trim whitespace from setting incident body override
now
date_add
Add 0 minutes to
deployments_raw
?
deployments
default
Apply default
failed_rows
filter
Filter by condition
production_failed_rows
filter
Filter by condition
existing_deployment_ids
map
Extract from each item
unhandled_failed_rows
filter
Filter by condition
candidate_rows
slice
Take a subset of
candidate_count
count
Count items in unhandled failed rows
has_candidate
compare
Check if candidate rows has data
deployment_id
default
Apply default
deployment_name
default
Apply default
deployment_project_id
default
Apply default
deployment_url
default
Apply default
deployment_ready_state
default
Apply default
deployment_error_code
default
Apply default
deployment_error_message
default
Apply default
has_deployment_id
compare
Check if deployment id has data
has_page_id
compare
Check if page id has data
skip_proposal
any
Check if any of the conditions are true
default_incident_name
template
Generate text from a template
skip: step.skip_proposal equal true
has_name_override
compare
Check if incident name override text has data
incident_name
ternary
Apply ternary
skip: step.skip_proposal equal true
default_incident_body
template
Generate text from a template
skip: step.skip_proposal equal true
has_body_override
compare
Check if incident body override text has data
incident_body
ternary
Apply ternary
skip: step.skip_proposal equal true
proposal_key
template
Generate text from a template
skip: step.skip_proposal equal true
write_proposal
?
skip: step.skip_proposal equal true
notify_enabled
compare
Check if setting notify owner equals true
should_notify
all
Check if all conditions are true
send_owner_notification
?
skip: step.should_notify not_equal true
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
vercel
setting
=
team id
setting
=
channels
setting
=
in_app
row limit
setting
=
10
team slug
setting
=
project id
setting
=
notify owner
setting
=
true
initial status
setting
=
investigating
impact override
setting
=
minor
deployment state
setting
=
ERROR
deployment target
setting
=
production
statuspage page id
setting
=
deliver notifications
setting
=
true
incident body override
setting
=
incident name override
setting
=
statuspage component ids
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.