AgentPlayground
Docs
n8n compatibility guidelines

Status: planned, not yet built.

The idea

A dedicated, machine-readable page — written so that when someone asks their coding assistant (for
example, "make my n8n workflow compatible with AgentPlayground"), the assistant can fetch this
exact page and follow explicit, literal conventions rather than guessing at the integration shape.

What it will document
  • The exact request/response shape of /api/brain/push (see Drive it from any LLM for what's real today) as a strict, copy-pasteable contract.
  • Recommended n8n node patterns for common cases (push a scraped result, push a form submission, route to a specific team folder via the team field).
  • Once n8n — let agents control n8n ships, the reverse contract: what a workflow an agent creates is expected to look like so it stays inspectable and safe.
Why it's a separate page from n8n — connect

n8n — connect AgentPlayground to n8n is written for a human setting up a
workflow by hand. This page is written for an LLM reading it autonomously — more explicit,
more structured, less prose. Same underlying integration, different audience.