Use “Vercel deployment investigation brief” in Recued. It provides a read-only Vercel deployment investigation brief.

How it works 13 steps

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

Process (13 steps)

■ deployment_id_or_url_trim trim

Trim whitespace from setting deployment id or url

■ team_id_trim trim

Trim whitespace from setting team id

■ team_slug_trim trim

Trim whitespace from setting team slug

◆ deployment recued-core.vercel.deployment.read

Read deployment on vercel

◆ events_raw recued-core.vercel.deployment.events.list

List deployment events on vercel

◆ aliases_raw recued-core.vercel.deployment.aliases.list

List deployment aliases on vercel

■ defaults defaults

Apply defaults

■ event_count count

Count items in events

■ alias_count count

Count items in aliases

✦ summarize core.ai.summarize

AI generates a concise summary

■ event_table to_table

Format results as a data table

■ alias_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

▼

Output

summary card

table event_table

table alias_table

json deployment.result

Settings 6 configurable

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

focus setting = Summarize deployment state, build or runtime failure indicators, aliases affected, checks state, error codes/messages, and recommended next actions.

team id setting =

team slug setting =

max length setting = 1000

event limit setting = 100

deployment id or url setting =