What's the difference between an AI agent and an automation?

Three intake forms, no shared home for any of them, until an afternoon with Zapier and Notion fixed it. The most common question I get is: "What is the difference between an agent and an automation?" SPOILER ALERT: yes, there is a difference.

For months, dainty.me's leads have been landing in three different places. Someone fills out the intake form on the website directly. Someone else joins through a launch event website. A third stream comes in from another event. Three forms, three small trickles of interest, and until this week, no single place holding all of them. It was making me G R E Y (OK, I was already, but this is not the point. Look away from my head).

I finally made time to sit down and fix it. I am not a developer and I did not need one. It is not a six-week build. It was one afternoon, a free Zapier account, a Notion database and two rolled-up sleeves.

Here's what I want you to take from this, more than the mechanics: the gap between "automation" and "agent" is smaller, and more useful, than the marketing around AI agents makes it sound. It is quite simple, but I'll make it simpler:

An automation is a fixed recipe. An agent adds a step in the middle: notice this happened, decide what it means, then act.

There is zero "reading" and no judgment in the first case. The 500th form fill gets treated exactly like the first one, on repeat. The second is the harder, more expensive build. Most small businesses don't need it yet. Most small businesses need the first thing, wired well.

What I built

So that's what I built. Two small automations, "Zaps" in Zapier's language, each doing one job:

• Zap 1: a new form fill on the DAINTY website creates a new row in a Notion database, tagged "DAINTY Website".
• Zap 2: a new form fill on the launch form lands in the same database, tagged "Launch", with the city mapped straight across.

That's the whole build. About ten minutes each, on Zapier's free plan, because each Zap is exactly one trigger and one action, which is what the free plan gives you before it asks for a card. From there, it plugs into Kit, my email software (by the way, also free). All it cost me was some time and some sparks between some neurons.

The real work sits upstream

The only real decision sat upstream of the automation itself. I set the city question on the launch form as a dropdown instead of free text: two options, exact spelling. An automation can only be as clean as the data feeding it, and a free-text field with "CT", "cpt" and "Cape Town" typed three different ways breaks the mapping before it starts.

Tech bros don't spell that out during the fire-dance and AI-agent hype ceremonies. The unglamorous work sits upstream, in how cleanly your form asks the question, not in the tool that moves the answer. DATA IS KING. Well, I prefer QUEEN.

Once it was live, I could see the shape of what comes next, because every business runs on the same pattern, whether it feels that way or not: something happens, and something should get written down or sent. A call gets booked, and a prep brief should go out. Someone says yes, and an onboarding checklist should appear. A referral comes in, and a thank-you should go out within the hour, not whenever I remember to send it.

Each one becomes a five-minute build once the first one exists. When the bones are good, the shape just repeats: trigger, then action. The skill isn't Zapier. The skill is noticing where a handoff currently lives only in your head, and moving it somewhere it can't be forgotten.

If you're staring at your own scattered forms thinking you should fix that, you probably should. Start with the smallest, most structured signal you have, a form, not an inbox, and wire just that one thing. You don't need the whole system on day one. I didn't.

Where to start

If the handoffs in your business live in your head, the Process Automation X-Ray asks you a few questions (or lets you just talk) and gives you a fully sequenced, AI-readiness-scored process document. That's what we automate from.