You can write a workflow as a plain-English SOP — the same way you'd document a process in Google Docs — and have an AI agent execute it step by step. The practical path today is Claude's tool-use API or n8n with an AI node for reasoning steps. Neither is fully no-code yet, but the gap between "writing down what should happen" and "making it happen automatically" is closing fast.
The idea is simple: write your process steps in plain English — exactly as you'd write an SOP you'd hand to a new employee — and have an AI agent execute them, step by step, in real time. This question came up in the r/ChatGPT community and reflects a broader shift in how people are thinking about automation.
Traditional workflow tools like Zapier, Make, and n8n require you to think in nodes, triggers, and data mappings from day one. That cognitive barrier locks out anyone who isn't already technical. The new paradigm flips this: describe what you want in natural language first, then either the AI interprets and runs it, or a translation layer maps your prose steps to executable actions.
A concrete example makes this tangible. Instead of building a multi-node flow from scratch, you write:
That's an SOP. Increasingly, that SOP can become the automation — not just documentation of it. For a broader look at where this fits in AI automation workflows, the tooling options are expanding rapidly.
The tooling is maturing fast but unevenly — here's an honest breakdown of what's available right now.
| Tool / Approach | Plain-English Input? | Executes Steps? | Shows Live Progress? | Best For |
|---|---|---|---|---|
| ChatGPT + Custom GPTs | Yes | Partial (via Actions) | Partial | Drafting, research, light API calls |
| Claude (Anthropic) | Yes | Yes (with tool use) | Yes (streaming) | Agentic tasks, multi-step reasoning |
| n8n + AI node | Somewhat | Yes | Yes | Technical teams wanting visual + AI hybrid |
| Make (Integromat) | Limited | Yes | Yes | Non-technical users, established integrations |
| Custom Agents (API) | Yes | Yes | Depends on build | Production-grade, domain-specific automation |
If you want the closest thing to "write steps in plain English and watch them execute," you're currently looking at Claude's tool-use API [1] or n8n with AI-powered step generation. Neither is fully plug-and-play for non-developers, but the ceiling is higher than most people realize. Claude supports structured tool calling natively, which is what enables an agent to decide which function to invoke at each step of your SOP. [1]
For teams already exploring Model Context Protocol, you can also use Buddy from Claude, ChatGPT, or Cursor via MCP to connect AI reasoning directly to advertising workflows without building a custom integration layer from scratch. MCP is an open protocol designed to let language models connect to external tools and data sources in a standardized way. [2]
Before touching any tool, write your workflow as a plain document. Include:
This document becomes your agent's system prompt skeleton. It's not preparatory work — it is the work. If you're looking to go deeper on structuring prompts for agent behavior, the principles of automating workflows with custom commands apply directly here.
Not every step needs a language model. Map your SOP steps into two columns:
Your choice depends on technical comfort and production requirements:
Watching steps execute in real time is operationally important, not just a nice UX feature. If your agent runs 12 steps and fails on step 9, you need to know exactly what happened at each prior step. Build in:
In Buddy, the AI Google Ads agent, step execution status is surfaced directly so anyone running an account audit can see exactly what the agent checked, in what order, and what it found — before it makes any recommendations. That transparency is what makes agents trustworthy in a business context.
A manual account audit SOP might run 15–20 steps: check campaign budgets, review impression share, flag keywords with high spend and low conversions, review ad copy performance, identify structural issues. Written as a plain-English document, this becomes a system prompt. The agent calls the Google Ads API [4] at each relevant step, runs analysis, and surfaces findings — in under 5 minutes versus the 2–3 hours a manual audit takes. This is precisely the workflow Buddy executes.
A typical SOP: new form submission arrives → enrich with a data provider → score based on ICP criteria → if score >70, route to AE Slack channel and create a CRM deal → if 40–70, enroll in nurture sequence → if <40, tag as low-priority. This maps cleanly to a tool-use agent: enrichment API call, scoring logic (LLM or rules-based), CRM API calls, Slack webhook. Fully automatable with plain-English-to-execution tooling today. If you want to explore more patterns like this, the advanced GPT workflow library covers a wide range of marketing-specific templates.
Pull data from GA4, Google Ads, and your CRM → calculate week-over-week changes → flag anything outside normal ranges → generate a plain-English summary → send to Slack or email. Teams that have built this report saving 3–5 hours per week of analyst time, consistently. Note: Universal Analytics stopped processing data in July 2023, so any reporting agent must connect to GA4 as the only Google Analytics data source.
LLMs can confidently make the wrong call at a decision branch, especially when the context window gets large or instructions are ambiguous. [5] Mitigation: be extremely explicit in your SOP about decision criteria. Don't write "if the lead looks qualified" — write "if the lead's company has >50 employees AND is in SaaS or eCommerce AND has filled out the budget field with a value >$5,000/month, route to AE." Specificity is your safety net.
APIs fail. Rate limits hit. Fields return null. Your agent needs retry logic, fallback behaviors, and alerting when a step fails. Most demo-level agents omit this entirely.
Running a 15-step agent across hundreds of leads per day adds up. Profile your token usage per workflow run early. Well-optimized agents with selective LLM use — only reasoning steps — typically run for $0.02–$0.08 per workflow execution on most marketing use cases. Naïve implementations that pass every step through the LLM can run 10x higher.
If your workflow spans more than a few minutes or waits for external events (e.g., waiting for an email reply before the next step), you need persistent state. Simple agent loops don't handle this well. Durable execution frameworks like Temporal or Inngest are worth evaluating for workflows with this pattern.
Not necessarily for simple workflows. Tools like n8n and Make let you build visual flows with AI nodes handling reasoning steps — no code required at the prototype stage. For production-grade agents with error handling, retry logic, and persistent state, some coding (Python or TypeScript) is typically needed. The no-code path is a valid starting point to validate the logic before investing in custom development.
Zapier handles deterministic, event-driven automation well — "when X happens, do Y." Plain-English AI agents add a reasoning layer: the agent can evaluate conditions, generate content, make judgment calls based on context, and adapt its path through the workflow. The two approaches are complementary; the AI agent pattern is most valuable where branching logic or language generation is involved, not for simple linear triggers.
Replace vague criteria with explicit, measurable conditions in your SOP. Instead of "if the lead seems promising," write out every qualifying attribute with specific thresholds — company size, industry, deal value, form fields completed. The more specific your instructions, the less the model has to infer. You can also add a human-approval step at high-stakes decision points rather than letting the agent proceed autonomously.
Yes. ChatGPT with custom GPT Actions or the OpenAI API with function calling supports the same tool-use pattern. [3] The practical difference is in streaming and multi-step agentic behavior — Claude has been optimized heavily for extended agentic tasks, while OpenAI's function-calling is robust for well-defined tool schemas. For most marketing workflows, either platform can work; the SOP-first methodology is the same regardless of which model you use.
Cost depends almost entirely on how selectively you use the LLM. Agents that route deterministic steps (API calls, data writes) directly — and only invoke the model for genuine reasoning — typically run for $0.02–$0.08 per workflow execution on marketing use cases. Agents that pass every step through the model can run 10x higher. Profile token usage on a small batch before scaling to hundreds of daily runs.
Without error handling, the agent either halts silently or proceeds with bad data — both are production-breaking outcomes. The correct pattern is to wrap every tool call with error handling, log the failure with context, and have the agent retry with exponential backoff or escalate to a human. For complex multi-step workflows, consider a durable execution framework like Temporal or Inngest if steps depend on external events that may take minutes or hours to resolve.
More answers in this topic: Automation & Scripts
