Skip to main content

See It End-to-End: The Full Demo

You've now seen every Circus node and the ideas behind them. The best way to make it all concrete is to run the full demo — The Hedgerow Herald, a complete working example that exercises Init, Agent, Log, Complete, and Terminate across three real workflows.

What the demo gives you​

The demo ships with the default plugin (in its demo/ directory) and includes three ready-made n8n workflows:

  • News Generator — takes a headline and briefing, and an Agent node writes a full report.
  • News Revision — takes an existing report plus operator feedback, and revises it.
  • Generate Media — reads a finished report, an Agent node writes an image prompt, then service calls (built the HTTP-Request-plus-Log way) generate an image and audio and upload the results.

Together they show the whole toolkit in action: operator-controlled Agent nodes, hand-built service calls with logging, error branches with Terminate, and Complete handing back all the artifacts at once.

The end-to-end setup lives in one place​

Rather than duplicate it here, the full walkthrough — configuring the platform and wiring up the n8n side — is the operator package's Demo: The Hedgerow Herald, End to End. That's deliberate: if you're a single-player running the whole thing yourself (developer, operator, and ops at once), you'll want both halves in order, and they're together there.

Your half: import and wire up​

The workflow-developer part is Part A of that walkthrough — importing the three JSON files into your n8n and assigning credentials:

  1. In n8n, Import from File each of the three demo workflow files.
  2. n8n will flag missing credentials — create and assign your own for each type: your Circus API key (on every Circus node), your AI provider key(s) (on the Agent nodes), the JWT webhook secret, and the service credentials the Generate Media workflow needs (xAI, ElevenLabs, and AWS for S3).
  3. Publish each workflow so Circus can trigger it in both test and production mode.
  4. Note each workflow's webhook path — you'll give these to the operator as the webhook identifiers when they register the workflows in Circus.

The demo includes a full pre-flight credentials checklist; missing credentials are the most common reason a workflow fails silently. Once everything's wired and the operator has configured the Circus side, add a Thing, run News Generator, and watch your workflow — and every node you've just learned — work end to end.