Skip to content

Workflow builder by chat

Builds automation workflows from plain language instructions instead of dragging nodes by hand. You review and test each workflow before turning it on.

EngineeringWorks with Claude Code · n8nCommunity example
Build your promptSee requirements

What it does

  • Turns your description into a workflow
  • Fills in nodes and settings
  • Explains each step it added

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Turning on the workflow
  • Adding new credentials

You decide what happens next.

More about this workflow

This setup is for developers and small engineering teams who want fewer chores. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it turns your description into a workflow. Next, it fills in nodes and settings. Finally, it explains each step it added. It works with your automation platform, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before turning on the workflow and adding new credentials, and says plainly if a step cannot be undone.

“I reviewed + tested it”
Awais Sultan @AwaisSultanz · Sep 12, 2026
Before you startAutomation platform accessScoped permissionsClaude Code or n8n
Explore required tools and model recommendations

Tools and access

  • n8n

    Handles the automation platform part of this job. Grant create workflows, left inactive until reviewed.

    API required: Yes. Needs an n8n API key from settings. New workflows should stay inactive until you review them.

    Sign up: n8n

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Opus 5.5

Its maker points to it for long running coding work.

$4 per million input tokens, $20 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Sonnet 5.5

Half the price per token and still strong for reviews and docs.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

2Your prompt

3 of 3 still empty
Fill these in before you run it: [THE AUTOMATION PLATFORM AND PROJECT] [WHAT THE WORKFLOW SHOULD DO] [WHO REVIEWS AND TESTS IT] You are the Workflow builder by chat agent. Builds automation workflows from plain language instructions instead of dragging nodes by hand. You review and test each workflow before turning it on. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Turns your description into a workflow - Fills in nodes and settings - Explains each step it added What you must never do without a yes from a person: - Turning on the workflow - Adding new credentials Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, n8n

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect n8n with its own login, not yours. Grant create workflows, left inactive until reviewed.
  2. 2Paste the prompt where your harness takes instructions. See the note under the Copy button.
  3. 3Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  4. 4Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access24 / 30

Writes drafts and notes inside your tools, nothing leaves on its own.

Human approval30 / 30

Waits for a yes on: turning on the workflow, adding new credentials.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope20 / 20

Runs on its own login across 1 tool. Fewer connections means a smaller blast radius.

How to raise it

This setup is already at its best possible score under our rubric. Nothing left to raise.

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Workflow builder by chat](https://trustcase.dev/badge/workflow-builder-by-chat.svg)](https://trustcase.dev/use-cases/workflow-builder-by-chat)
HTML
<a href="https://trustcase.dev/use-cases/workflow-builder-by-chat"><img src="https://trustcase.dev/badge/workflow-builder-by-chat.svg" alt="Trustcase trust score for Workflow builder by chat" height="20"></a>

More engineering workflows

  • Meeting notes to issues

    Turns meeting notes into draft issues and specs so follow ups do not get lost. You review the list before anything is filed.

  • Broken link sweep

    Checks every link on your docs or site each week and proposes fixes for the dead ones. A person confirms each fix before it goes live.

  • Weekly codebase review report

    Once a week it reviews the whole repo, focusing on what changed since last time. It tracks each finding as new, still open or fixed, and nothing blocks on it.

  • Small fix pull requests

    Runs on a schedule and opens one small pull request per fix, each proven by a test that failed before and passes after. Changes collect on a dev branch and you decide when they ship.