Automation and No-Code

Act as a no-code automation specialist who builds workflows for freelancers and small businesses. I want to stop digging through my inbox for receipts, paid bills and invoices every time I close the month. My setup: - Email I use: gmail_outlook_other - Where I want to store the files: google_drive_onedrive_dropbox - Where I want the expense list: google_sheets_excel_notion - Tools I am willing to use: zapier_make_n8n_power_automate_or_no_preference - Average volume per month: number_of_receipts - Who uses this afterwards (me, accountant, business partner): recipient Build the workflow following these steps: 1) Detection rules: senders, subject keywords and attachment types that signal a receipt, and how to avoid catching promotional emails. 2) The automation step by step, trigger by trigger, with the exact name of each module in the chosen tool. 3) A file naming pattern and a folder structure by year, month and category. 4) Spreadsheet columns (date, vendor, amount, category, payment method, file link) and how to pull that data from the email body or the PDF. 5) What to do with items the automation cannot recognize: a manual review label and a weekly reminder. 6) An automatic monthly summary sent to recipient. Present the steps in a table with trigger, action and tool. Flag the free plan limits of each tool that could break the workflow and ask me to confirm current numbers on the pricing page. Never suggest sharing my email password with third-party services; use only official sign-in connections.

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.

Act as a customer service consultant for small businesses who sets up WhatsApp Business without any coding. About my business: - Industry: e.g. clinic, restaurant, clothing store, service provider - Business hours: days and times - Questions I get the most: list up to 10 - What I sell or book through WhatsApp: products, services, reservations - How long I currently take to reply: average time - Tool: just the WhatsApp Business app or a chatbot platform I already use - Tone of voice: formal, friendly, casual Create the customer service package: 1) A greeting message for first-time contacts, with up to 3 numbered topic options. 2) An away message for after hours, saying when I will reply. 3) Quick replies for each question on my list, with a short suggested shortcut for each. 4) A triage flow showing what the automation handles on its own and at which point the chat is handed to a person. 5) Labels to organize chats, such as new contact, quote sent, awaiting payment and order completed. 6) A follow-up message for people who asked for a quote and have not replied within time frame. Message rules: no more than 4 lines each, no promises I cannot keep and no promotions to anyone who has not opted in. Deliver everything in a table with the columns situation, trigger, ready-to-send message and notes.

Act as a no-code automation specialist. I have an automation in tool: Zapier, Make, n8n or another that does describe what it does and connects list the apps involved. It runs frequency and has already failed in these situations describe the errors you have seen. Follow these steps: 1) List every point where this automation can break, separating connection failures, data in an unexpected format, rate limits, duplicated items and steps that ran only halfway. 2) For each point, give the right handling: retry with progressive backoff, alternate path, validation before writing, and an idempotency check so records are not duplicated. 3) Describe how I find out when something fails, including the alert channel, what the message must contain and what is not worth notifying. 4) Build a recovery plan explaining how to reprocess what was missed without repeating what already succeeded. 5) Suggest one simple test per risk, including the input I should use to trigger the failure on purpose. Format: a table with Risk, Symptom, Handling and Test, followed by a checklist of what must be in place before I let this automation run unattended.

Act as a no-code automation consultant with hands-on experience in Zapier, Make and n8n. I will describe the workflow I want to automate and you will recommend the right tool for my case. My workflow today: describe step by step, from trigger to result Tools involved: e.g. Gmail, Google Sheets, Notion, WhatsApp Estimated volume: e.g. 300 runs per month Monthly budget: amount Who will maintain it: me, a technical team, or nobody Data constraints: e.g. customer data, must stay self-hosted Deliver: 1. A table comparing Zapier, Make and n8n for my case, covering estimated cost at my volume, learning curve, available integrations and maintenance effort 2. One single recommendation, with the reason in two sentences and the conditions under which that choice would stop making sense 3. The workflow designed in the chosen tool, with trigger, steps and conditions 4. The points where the automation is likely to break and what to do about each 5. What to test before turning it on in production 6. The signals that it is time to migrate to a different tool If my case does not justify automation at all, say so and explain why.

Act as a process automation consultant fluent in no-code tools such as Zapier, Make, n8n, Power Automate and Apps Script. I want to automate a manual task I repeat every week. Task: describe step by step what you do today, start to finish. Frequency: times per week. Time spent each run: minutes. Tools I already use: spreadsheets, email, CRM, messaging, ERP. Monthly budget: amount. My technical level: none, intermediate, I can code. Follow these steps: 1) Rewrite the current process as a numbered trigger, actions and decisions, marking where human judgment is required. 2) Say what is worth automating, what is only worth standardizing and what should stay manual, with the reasoning for each call. 3) Propose two solution scenarios, one simpler and cheaper and one more robust, with the tools, estimated cost and implementation effort. 4) Detail the recommended flow with trigger, steps, conditions and error handling. 5) Estimate hours saved per month and the payback period. 6) List the risks, such as silent failures, rate limits and sensitive data, with a mitigation for each. Present steps 2, 3 and 6 as tables. If you are missing information needed to decide, ask before proposing.