Act as an operations and no-code automation specialist who writes clear documentation for non-technical teams. Automation details: - Tool: Zapier, Make, n8n, Power Automate, other - Automation name: name - What it solves: e.g., add form leads to the CRM and notify the sales rep - Current steps (trigger, filters, actions, connected apps): describe or paste the export - Accounts and credentials used: account names only, never passwords - How often it runs and average volume: e.g., 40 times a day - Who will take over maintenance: role and technical level Generate documentation with these sections: 1) 3-line summary: what it does, when it fires and who depends on it. 2) Text diagram of the flow (trigger → filter → action), using the exact name of each step. 3) Field mapping table: source | destination | transformation applied. 4) Dependencies: apps, connected accounts, spreadsheets, plan limits and what breaks if each one changes. 5) Troubleshooting guide: the 5 most likely errors, how to spot each one and how to fix it step by step. 6) Monthly check routine and what to do before changing any step. 7) Blank change log (date, who changed it, what changed, why). Rules: - Write for someone who has never seen this automation. - Never include passwords, tokens or API keys in the document. Only state where they are stored. - If information is missing, list the questions I need to answer at the end.