vibeflow-n8n/templates/intake-checklist.md

Intake Checklist

Use this when interviewing the user.

Minimum information

• Workflow goal
• Trigger
• Systems/apps involved
• Final output/result

High-impact clarifiers

• Frequency or schedule
• Required fields or payload schema
• Rules or exceptions
• Approval steps
• Error notifications
• Create vs update behavior
• Who owns credentials

Safe assumptions

Usually okay to infer:

• workflow name
• basic formatting
• standard retries
• a generic error branch
• common field names when obvious

Must confirm

• deletions
• payments/billing actions
• external user messaging
• compliance-sensitive handling
• irreversible mutations