sample generated handoff

What the buyer gets after pasting workflow JSON.

This is sample Markdown output from the tool. The buyer can copy it into Notion, Google Docs, or a project portal, then add client-specific business outcome and test evidence.

Generated Markdown Sample From a sample new-lead intake workflow
Get the tool
# New Lead Intake to Quote Follow Up - Client Handoff

## 1. Plain-English Summary

This workflow starts from Website Lead Form and moves work through 6 active steps. It touches email send, google sheets, webhook.

Business outcome:
- Replace this line with the client-facing result in one sentence.
- Example: "When a new lead arrives, the owner gets a clean notification and the lead is logged for follow-up."

## 2. Trigger And Inputs

Trigger nodes:
- Website Lead Form (webhook)

Inputs expected:
- What data starts the workflow?
- Which fields are required?
- What should happen if a required field is missing?

## 3. Systems And Access

Systems touched:
- email send
- google sheets
- webhook

Credentials to confirm:
- Add Lead to Sheet: Owner Google Sheets
- Send Owner Email: Support inbox

## 4. Workflow Map

- Website Lead Form -> Normalize Lead Fields
- Normalize Lead Fields -> Add Lead to Sheet
- Normalize Lead Fields -> Send Owner Email
- Send Owner Email -> Follow Up Delay
- Follow Up Delay -> Send Prospect Follow Up

## 5. Step Inventory

1. Website Lead Form - webhook
2. Normalize Lead Fields - set
3. Add Lead to Sheet - google sheets
4. Send Owner Email - email send
5. Follow Up Delay - wait
6. Send Prospect Follow Up - email send

## 6. Owner-Safe Changes

The client or owner can usually change these safely after handoff:
- Email copy.
- Notification recipients.
- Spreadsheet column labels only if downstream references are updated.
- Schedules and wait times.
- Routing thresholds that were documented during delivery.

Do not change these without testing:
- Field names used by later steps.
- Credentials.
- HTTP request URLs.
- Code nodes.
- Branching conditions.

## 7. Break-Fix Checklist

If the workflow stops working:
1. Check whether the trigger received a new event.
2. Check the first failed node in the execution log.
3. Confirm credentials are still connected.
4. Confirm external services are reachable.
5. Test with one known-good sample input.
6. Restore the last working version if a recent edit caused the issue.

Risk notes:
- No dedicated error trigger was detected. Add or document the owner alert path before delivery.
- Email nodes should have sender, reply-to, opt-out, and deliverability expectations documented.

## 8. Delivery Notes

Delivered files:
- n8n workflow export.
- This handoff document.
- Test input or screenshot of a successful execution.

Acceptance check:
- Owner understands what starts the workflow.
- Owner knows where data goes.
- Owner knows what they may safely edit.
- Owner knows who to contact if a credential or outside service breaks.