Write a spec for a Zapier, Make or n8n automation
For describing an automation clearly before you (or someone you hire) builds it.
- Teams
- Operations
- Job:
- Plan
- Level:
- Everyday
- Saves about:
- 20–45 min (our estimate)
What you'll get
Example run in Claude on 6 Nov 2026
**1. Trigger** Tally: new form response on the "Request a quote" form. **2. Steps** 1. HubSpot: find a contact by email; if none, create one with name, email, phone and source "Quote form". 2. HubSpot: create a deal named "[Name] – [Job type]" with the estimated value from the form. 3. Gmail: send the thank-you email from the sales inbox, using the first name and job type. 4. Slack: post in #sales with name, job type, value and a link to the deal. **3. Filters and conditions** - Path: if the estimated value is over $10,000, also send a Slack direct message to the manager and set the deal owner to the manager. **4. When something fails** - Turn on Zapier's error emails to the operations inbox. - If the HubSpot step fails, still send the Slack message, marked "not in CRM", so no lead is lost. **5. Tests** 1. A new person with a small job: contact, deal, email and #sales post all appear. 2. The same email again: no duplicate contact. 3. A $12,000 job: the manager gets a direct message and owns the deal. **6. Questions for you** - Is the estimated value a number field on the form, or free text? - Should the thank-you email come from a person or a shared address? - Which deal pipeline and stage should new deals start in?
AI answers vary from run to run. Check facts, figures and names before you use a result.
Fill in your details
What you type stays in this browser tab. Don't paste passwords, card numbers or personal details you aren't allowed to share with an AI assistant.
Your prompt
You are an automation consultant. Turn my description into a clear spec someone can build in Zapier. What should happen: [What should happen] Apps involved: [Apps involved] Return: 1. Trigger: the exact event that starts it. 2. Steps: numbered, each with the app, the action, and the fields it uses. 3. Filters and conditions. 4. What should happen when something fails. 5. How to test it with three sample cases. 6. Anything I haven't told you that the builder will need to ask.
2 details still to fill in. You can also copy it as it is and fill them in yourself.
Opening in an assistant also copies the prompt, so you can paste it if it doesn't appear. Works in any chat assistant, including ChatGPT, Claude, Gemini and Microsoft Copilot.
Tips
- Share the spec with whoever builds it; it doubles as their test plan.
- App Scavenger's automation recipes show tested setups for common cases.
Apps this helps with
More prompts for operations
Customer support · Advanced
Find patterns in a batch of support tickets
For a weekly or monthly look at what customers keep asking, to fix the causes.
Saves 60–120 minOperations · Quick
Turn meeting notes into decisions and action items
For sending a clear recap right after a meeting, so nothing gets lost.
Saves 10–20 minOperations · Everyday
Write a step-by-step process (SOP)
For writing down how a task is done, so anyone on the team can do it the same way.
Saves 30–60 min
