Name: Create approved Statuspage incident from Vercel failure
Author: recued-core

Create approved Statuspage incident from Vercel failure

by recued-core v1 9 views

Use “Create approved Statuspage incident from Vercel failure” in Recued. It carries out the named workflow using the connections and settings you choose.

Complete workflow

Deployment Incident Loop - Vercel + Statuspage 2 pinned recipes

Use Deployment Incident Loop - Vercel + Statuspage in Recued for deployments, incidents, customer communications, and closed loop. It includes 1 ready-to-run workflow and 2 related packs in one install.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Create approved Statuspage incident from Vercel failure

This recipe

Use “Create approved Statuspage incident from Vercel failure” in Recued. It carries out the named workflow using the connections and settings you choose.

vercelstatuspagedeploymentincident

by recued-core pinned v1

Propose Statuspage review for failed Vercel deployment

Background automation

Use “Propose Statuspage review for failed Vercel deployment” in Recued. Scheduled detection half of the Vercel to Statuspage incident loop.

vercelstatuspagedeploymentincident

by recued-core pinned v1

View pack details, dependencies, and permissions →

How it works 48 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Data fetch

▼ proposals ?

▼

Process (47 steps)

■ proposals_family filter

Filter by condition

■ requested_deployment_id trim

Trim whitespace from setting proposal deployment 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

■ incident_status_override_text trim

Trim whitespace from setting incident status override

■ impact_override_config trim

Trim whitespace from setting impact override

■ pending_proposals filter

Filter by condition

■ has_target_deployment compare

Check if requested deployment id has data

■ targeted_proposals filter

Filter by condition

■ selected_pool ternary

Apply ternary

■ candidate_proposals slice

Take a subset of

■ pending_count count

Count items in pending proposals

■ has_candidate compare

Check if candidate proposals has data

■ proposal_key default

Apply default

■ statuspage_connection default

Apply default

■ defaults defaults

Apply defaults

■ component_override_count count

Count items in setting component ids override

■ has_component_override compare

Check if component override count is greater than 0

■ component_ids ternary

Apply ternary

■ has_name_override compare

Check if incident name override text has data

■ incident_name ternary

Apply ternary

■ has_body_override compare

Check if incident body override text has data

■ incident_body ternary

Apply ternary

■ has_status_override compare

Check if incident status override text has data

■ incident_status ternary

Apply ternary

■ has_impact_override compare

Check if impact override config has data

■ incident_impact_override ternary

Apply ternary

■ action_is_create compare

Check if setting action equals create_incident

■ action_is_dismiss compare

Check if setting action equals dismiss_no_customer_impact

■ has_connection compare

Check if statuspage connection has data

■ has_page_id compare

Check if page id has data

■ has_incident_name compare

Check if incident name has data

■ has_incident_body compare

Check if incident body has data

■ ready_to_create all

Check if all conditions are true

■ ready_to_dismiss all

Check if all conditions are true

■ now date_add

Add 0 minutes to

■ mark_proposal_dismissed ?

skip: step.ready_to_dismiss not_equal true

■ create_incident ?

skip: step.ready_to_create not_equal true

■ created_incident_id default

Apply default

■ has_created_incident compare

Check if created incident id has data

■ mark_proposal_created ?

skip: step.has_created_incident not_equal true

■ link_deployment_to_incident ?

skip: step.has_created_incident not_equal true

■ first_component_id default

Apply default

■ has_first_component compare

Check if first component id has data

■ skip_component_link any

Check if any of the conditions are true

■ link_incident_to_component ?

skip: step.skip_component_link equal true

■ summary to_summary

Format results as a summary card

Settings 9 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

action setting = create_incident

statuspage setting =

impact override setting =

deliver notifications setting = true

component ids override setting =

incident body override setting =

incident name override setting =

proposal deployment id setting =

incident status override setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Read your Statuspage connection

Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.verceldata.statuspagedata.shared

About

recued-core

Details

48 steps 9 configurable settings recipe_id: create-approved-statuspage-incident-from-vercel

Create approved Statuspage incident from Vercel failure

Complete workflow

Trust & control

Permissions it requires

Data it touches

About

Tags

Details