Skip to content
One Agent a DayIn → agent → out

Issue 23 · 27 Sep 2026 · Easy · Free

Automation Recipe Writer

The job is a habit in someone's head, and the automation tool is open on a blank canvas with no first step.

Describe a repetitive job. Get a trigger, filters, actions, and a failure step you can rebuild in n8n, Make, or Zapier.

Category
Automation
Runs in
ChatGPT
Claude
Gemini
Tags
Workflows
Automation
No Code

What you put in and what you get out

You put in

Describe the job as a habit. Write when it starts, what it must ignore, what it writes, and what should happen when a step fails. Name the tools you might rebuild it in.

Agent

Automation Recipe Writer

You get out

The slot. The sheet credential is named as a slot. The recipe does not contain a key.

Sample you can paste

Job: when a refund is requested in our form tool, post a summary to the #billing channel and add a row to the refunds sheet.
Trigger we have: the form tool can POST a webhook. It cannot poll.
Fields in the webhook: order_id, amount, reason, email.
Filter: ignore amount under 1 EUR. Those are tests.
Failure: if the sheet append fails, post to #billing with the word FAILED and do not retry more than twice.
Do not put the customer's email in the channel message. The sheet may have it.
Tools I will rebuild this in: n8n or Make. I do not want a Zapier-only binary.
Copy the promptDownload .txt

Share this agent

Automation Recipe Writer — You put in Job: when a refund is requested in our form tool, post a summary to the #billing channel…. You get out The slot. Free from One Agent a Day.

Share on XShare on LinkedIn

30-second demo

0:00

The habit

A form webhook creates a billing post and a sheet row. Amounts under 1 EUR are tests. Email stays out of the channel.

How it works

A recipe is a trigger, a filter, the actions, and the way it fails. You describe the habit and the fields you have. The writer returns steps you can rebuild in more than one tool, because the value is the shape, not a vendor file.

Secrets are slots, not values. A field you did not list cannot appear as a required input. The failure step is explicit: what gets posted, and when to stop retrying.

Build it, then send two test payloads: one the filter should drop and one it should keep. If the channel message contains a field you banned, the recipe is wrong.

Use it

  1. Step 1

    Describe the job as a habit

    Write when it starts, what it must ignore, what it writes, and what should happen when a step fails. Name the tools you might rebuild it in.

  2. Step 2

    Paste the fields you actually have

    List the webhook or export fields. The recipe cannot require a field you did not name.

  3. Step 3

    Paste the prompt

    You get a trigger, filters, actions, and one failure step. The shape is plain enough for n8n, Make, Zapier, or a script.

  4. Step 4

    Build it in the tool, secrets in the tool

    Create the credentials in the automation product. Do not paste API keys into the chat. Run one test payload under the filter and one above it.

Prompt

automation-recipe-writer.prompt.txt

Download
You write an automation recipe from a habit the human described. The recipe must be rebuildable in n8n, Make, or Zapier. You do not emit a vendor export and you do not ask for secrets.

INPUTS
- The job, in sentences.
- Trigger they can actually fire.
- Fields available.
- Filters and failure rules.
- Fields that must not appear in certain destinations.

RULES
- Steps in order: Trigger, Filter, Actions, Failure.
- Use only fields they listed. If a step needs a missing field, stop and name it.
- Secrets are named slots ("Sheet credential"), never values.
- Failure includes what is reported and the retry limit they gave. If they gave none, use two tries and say you assumed it.
- Do not add a step they did not ask for, including an email to the customer.
- A banned field must be absent from the destination they named. Say so in the step.
- Plain language. No product-only code.

OUTPUT
## Trigger
## Filter
## Actions
Numbered.
## Failure
## Test payloads
Two example payloads: one dropped, one kept. Use fake ids.
## Assumed
Or "None."

Config

automation-recipe.defaults.json

Download
{
  "version": 1,
  "steps": [
    "trigger",
    "filter",
    "actions",
    "failure"
  ],
  "defaultRetries": 2,
  "secrets": "slots-only"
}
Was this useful?

A yes or no is enough. The note stays on this server's log.

Related agents

  1. Automation30 Sep 2026 · #26Webhook Contract WriterPaste a sample webhook body. Get required fields, the idempotency key, retry behavior, and how you will verify the signature.InSample POST body from the form vendor, sent to us:OutThe checkAdvanced
  2. Automation15 Sep 2026 · #11Cron to Plain EnglishPaste a cron line, a systemd OnCalendar, or a GitHub schedule. Get plain English, the timezone trap, and the line you meant.InHost timezone: America/New_York.OutThe fixMedium
  3. Gaming14 Oct 2026 · #40Steam Backlog PickerPaste your Steam library and the evening you actually have. Get one game to launch, two backups, and a reason you can argue with.InEvening: 45 minutes, tired, controller, solo.OutBackups and the cutsEasy

Tomorrow's drop

Get the next agent in your inbox

One email when the drop goes up. No digest, no course. Unsubscribe whenever the provider lets you.

Pro and custom

€9/month when Pro opens

Early look at the next drop, a better archive, and the occasional agent that does not fit the public mix. The daily agent stays free. A custom build is €49–199. Nothing is charged from this form.

Join the Pro waitlist