Skip to content

Build Agents

Spawnbase gives you two ways to build agents: describe what you want in the copilot chat, or drag-and-drop nodes on the visual canvas. Most people start with the copilot and refine on the canvas.

Open the copilot panel (press A or click the chat icon in the footer) and describe what you want to automate:

Every morning at 9am, pull unresolved Sentry issues from the last 24 hours,
group them by root cause, rank by severity, and post a summary to #engineering in Slack

The copilot understands your intent, plans the workflow structure, and builds the nodes on the canvas. You review the plan, approve it, and the agent is ready to configure and deploy.

The copilot can also modify existing agents — ask it to add a step, change a schedule, or swap an integration.

The canvas is a visual workspace where your agent’s nodes and connections live. Each node is a step in the workflow, and edges show how data flows between them.

Working with the canvas:

  • Add nodes — press N to open the node picker, or right-click the canvas
  • Connect nodes — drag from a node’s output handle (right) to another node’s input handle (left)
  • Configure nodes — click any node to open its configuration panel on the left
  • Pan and zoom — scroll to zoom, drag the canvas to pan (or switch to select mode with V)
  • Annotate — add sticky notes to document your workflow logic

Every agent is built from four types of nodes:

Every agent starts with a trigger. It determines when and how the agent executes.

TriggerWhat it does
ScheduleRuns on a cron schedule — hourly, daily, weekly, or custom
ManualRuns on demand via button click or API call

The AI Agent node is what makes Spawnbase agents intelligent. It calls an LLM (Claude, GPT-4o, Gemini, Grok, and others) to reason about data, make decisions, and generate output.

Without tools, it makes a single LLM call — good for summarizing, classifying, or generating text. With tools enabled (web search, code sandbox, MCP servers), it becomes an autonomous agent that reasons, acts, and iterates until the task is done.

App action nodes call external services — send a Slack message, create a Linear issue, query PostHog analytics, or any of 25+ supported apps.

You pick an app, connect your account (OAuth or API key), choose a tool, and map inputs from upstream nodes.

Sticky notes for documenting your workflow. Non-executable — they’re just for you and your team.

Data passes between nodes through template variables. Each node’s output is available to downstream nodes:

{{schedule_trigger.output}}
{{sentry_issues.result}}
{{ai_summary.text}}

Click any node to see its output schema and available fields. The configuration panel shows which variables you can reference.

Before deploying, test your agent to make sure it works:

  1. Click Run in the header
  2. Watch execution in real-time in the bottom panel — each node lights up as it runs
  3. Click any node during or after a run to inspect its input/output
  4. Fix issues and re-run

The execution panel shows timing, status, and full I/O for every step. If a node fails, you see the exact error and can fix it without guessing.

ShortcutAction
AOpen copilot chat
NOpen node picker
VSwitch to select mode
HSwitch to pan mode
BackspaceDelete selected node
Cmd + ZUndo
?Show all shortcuts