The blank canvas eats the afternoon
Node search. Docs tab. One expression that keeps returning undefined.
AI workflow builder for the n8n you run
Deploy your Production workflows on autopilot
Describe the automation. Get it running. We build it in your own n8n, run it for real, and fix what breaks. You just paste the credentials.
Connects in two minutes. Any n8n 2.x you host. Nothing to migrate.
When a Stripe invoice is paid, add a row to Sheets and post to Slack.
Reading the request
- Invoice paidStripe triggerNot planned
- Add a rowGoogle SheetsNot planned
- NotifySlackNot planned
Step 1 of 8
Your workflows land in the tools you already pay for
Ten seconds to decide. Four hours to build.
Paid invoice, Sheets row, Slack ping. You knew that instantly. The wiring is what costs you the day.
Generic AI hands you JSON that will not import
It guesses node types your instance does not have. The import throws.
The workflow dies and nobody tells you
A token expires. The data stops. You hear about it a week later.
Three steps. None of them is wiring a node.
The workflows land in the n8n you already have. Nothing to migrate or relearn.
- 01
Paste your n8n URL and key
Two minutes. Nothing on your instance changes.
- 02
Say what you want automated
Plain sentences. Built from the nodes your instance actually has.
- 03
Walk away with it running
It runs for real, repairs what fails, and waits for you before anything live.
Or never leave your editor at all.
Same builder, same instance, same live test. Every approval gate still applies when the caller is a model.
- Claude
- Claude Code
- Cursor
- Windsurf
Read only
search_nodesget_nodeget_workflow_patternsget_best_practices
Writes, labelled as such8 tools
Tools that change a workflow are annotated in the protocol, so your client can ask you before they run.
n8n_create_workflown8n_update_workflowadopt_n8n_workflow
Touches production, flagged destructive
n8n_execute_and_diagnosen8n_heal_workflown8n_watch_workflowupdate_native_workflowrestore_workflow_snapshot
Ship fast without ever losing what already works.
Every change snapshots the workflow first. Break something at 4pm, be back on the working version before your coffee goes cold.
- See exactly what changed before it ships
- Which nodes moved, which parameters changed, what validation caught. You approve a diff you can read.
- “What was running last Tuesday?” has an answer
- Every change writes a snapshot and a record, and neither is edited in place. History cannot be quietly rewritten.
- One click back to working
- A rollback writes a new version rather than erasing one. You recover in seconds and the trail stays honest.
- Your team never overwrites each other
- Writes are checked against the version they were based on. A stale write is rejected, not silently accepted.
Know it broke before your team does.
Automations die quietly. You get the broken node, its error, and the reason, usually before anyone downstream notices.
- You find out before your users do
- Executions are watched as they run. You get told which node broke, while there is still time.
- The reason is on screen, not buried in JSON
- The node, the error n8n recorded, and how far the run got. One glance, not a midnight dump.
- Secrets never reach our database
- Credentials and payloads are redacted before anything is stored.
- New lead
webhookPassed12 ms1 item - Extract details
setPassed19 ms1 item - Enrich company
httpRequestFailed842 msHTTP 422Field company.name is requiredThe provider moved it under company.profile. - Qualified?
ifNot run - Notify sales
slackNot run
Guard
Broken at 3am. Fixed by the time you wake up.
Self healing sounds great until a model edits production on a hunch. Guard works to a fixed contract instead, and every boundary below is enforced in code.
- 1
Diagnose
Read the runtime data the failing node actually received. No guessing.
- 2
Patch
Allowlisted operations only. A model cannot invent a node type or write raw code.
- 3
Replay
Run the fix against the test input you saved. Nothing ships on an argument.
- 4
Verify
A pass keeps the fix. A regression restores the version that worked.
Contract, enforced in code
- 3
- attempts, then the circuit opens
- 15
- minute deadline per repair
- 1
- repair worker per workflow
- 0
- unlisted patch operations allowed
Five jobs you do today. Here is what they cost tomorrow.
Nothing here replaces n8n. It replaces the hours you spend wiring it.
| Job | On n8n alone | With PulserNode |
|---|---|---|
| Getting one built | An afternoon of node search, docs tabs, and expressions that return nothing. | One sentence. Nodes that exist on your instance, wired and ready. |
| Knowing it works | Trigger it by hand and squint at the execution log. | A real execution passes before anyone calls the job done. |
| Shipping a change | Export JSON, import it, reconnect credentials, repeat. | Every build leaves a version and a deployment record you can point at. |
| Undoing a change | Hunt for the export you hope somebody took. | One click back to any version, recorded as a new version. |
| When it breaks later | Someone reports it, or you spot the gap in the data days later. | Executions are watched as they run, and repairs stay inside your limits. |
The questions people ask before they connect an instance.
Short answers, written by the people who built it.
Not here? Email hello@pulsernode.com
What does PulserNode actually do?
You describe an automation in plain language and PulserNode builds it into the n8n instance you already run, then triggers a real execution and repairs what failed until it works. You approve the plan first, and anything with a live side effect waits for you.
How is this different from an AI that writes n8n JSON?
A general model writes node types from memory, so the JSON often fails to import. PulserNode reads the node catalog off your own instance first, builds against what is installed there, and proves the workflow by running it. You get a workflow that ran, not a file to debug.
Does PulserNode replace n8n?
No. You keep your own n8n and keep editing in its editor. PulserNode connects over the public API and adds the layer around it: an AI builder, version history, monitoring, and bounded repair. There is no second editor to learn and nothing to migrate.
Do I have to give PulserNode my n8n API key?
Yes, and it is the only credential we hold. It is envelope-encrypted at rest, decrypted only for an outbound call to your instance, and never returned to the browser. Disconnect the instance at any time and our access is revoked immediately.
Which versions of n8n work with PulserNode?
Self-hosted n8n 2.x reachable over HTTPS with the public API enabled. On connect, PulserNode probes the instance and tells you which capabilities it found, rather than failing later on a call your version does not support.
Can the AI change my production workflows without asking?
No. Model output is parsed into an allowlisted set of patch operations and anything else is rejected before it reaches your instance. Changes need your explicit approval, and automatic repair only runs on workflows you enrolled yourself.
What happens if a repair makes things worse?
The patched workflow is replayed against your saved test input and compared to the baseline. A regression restores the previous snapshot. Repair stops after three attempts or fifteen minutes and hands control back to a person.
Does PulserNode store my workflow data?
It stores workflow structure, version snapshots, and sanitized execution summaries. Business payloads are not retained, diagnostics are redacted before storage, and encrypted diagnostic samples expire after 30 days.
Can I use PulserNode from Claude or Cursor?
Yes. PulserNode runs a Streamable HTTP MCP server that Claude, Claude Code, Cursor, and Windsurf all connect to. The tools call the same API the web app does, so every approval gate applies when the caller is a model.
What does it cost?
Basic is $9 a month, or $7.20 a month billed annually, and covers version history, validation, rollback, and MCP access. AI Pro is $39 a month, or $31.20 a month billed annually, and adds unlimited AI workflow building, monitoring, and automatic repair. Founding seats take 40% off while they last.
The automation you keep putting off ships tonight.
Connect your n8n, describe the first one, and get back to your actual work.