Name: Create an incident.io follow-up
Author: recued-core

Create an incident.io follow-up

by recued-core v1

Approval-gated incident.io follow-up creation workflow. It reads the target incident, existing follow-ups, teams, and users for context, then creates exactly one follow-up through recued-core.incidentio.follow_up.create with caller-supplied title, description, assignee, team, priority, category, external reference, and labels. It does not edit incidents, update or delete existing follow-ups, create actions, mutate schedules, escalations, status pages, settings, API keys, or call arbitrary incident.io APIs.

How it works 17 steps

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

Process (17 steps)

■ incident_id trim

Trim whitespace from setting incident id

■ title trim

Trim whitespace from setting title

■ description trim

Trim whitespace from setting description

■ assignee_id trim

Trim whitespace from setting assignee id

■ assignee_team_id trim

Trim whitespace from setting assignee team id

■ external_issue_reference_id trim

Trim whitespace from setting external issue reference id

■ follow_up_category_id trim

Trim whitespace from setting follow up category id

■ follow_up_priority_option_id trim

Trim whitespace from setting follow up priority option id

■ has_title compare

Check if title has data

■ incident ?

■ existing_follow_ups ?

■ teams ?

■ users ?

■ skip_create compare

Check if has title does not equal true

■ created_follow_up ?

skip: step.skip_create equal true

■ existing_count count

Count items in existing follow ups result

■ card to_summary

Format results as a summary card

Settings 10 configurable

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

title setting =

labels setting =

incidentio setting =

assignee id setting =

description setting =

incident id setting =

assignee team id setting =

follow up category id setting =

external issue reference id setting =

follow up priority option id setting =

Trust & control

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

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Incidentio connection

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

About

recued-core

Details

17 steps 10 configurable settings recipe_id: create-incidentio-follow-up