Back to Documentation

Building Automations

20 steps - 10 minutes

Learn how to build AI-powered automations to streamline your workflows.

What are Automations?

Automations are graph-based AI workflows built with ReactFlow. They consist of nodes (trigger, agent, guardrail, human_approval) and edges (connections). Agent nodes use data.config.persona_id, prompt_id, context_ids, and tools (namespaces/subtools). Execution uses SSE streaming with events stored in automation_run_events table. Test runs execute using the current in-builder (unsaved) state.

1

Navigate to Automations

From the sidebar, click on "Automations" to access the automation builder.

2

Click "Create Automation"

Click the "Create Automation" button to start building a new workflow.

3

Enter Automation Name and Description

Give your automation a descriptive name (e.g., "Daily Email Summary", "Lead Qualification") and add a description explaining what it does.

4

Understanding the Visual Builder

The builder uses ReactFlow for the graph-based workflow. You can drag nodes, connect them with edges, and configure each node. The graph structure includes nodes (trigger, agent, guardrail, human_approval) and edges (connections).

Schedule Trigger
Daily at 12:00 AM
5

Choose a Trigger Type

Select how your automation starts: Schedule (cron-based), Webhook (external trigger), App Event (platform event), or Manual (on-demand).

6

Configure Trigger Settings

For scheduled automations, set the cron expression. For webhooks, copy the webhook URL. For app events, select the event type.

AN
Agent Node
No task set
7

Add an Agent Node

Drag an Agent node onto the canvas from the node palette. This is where the AI will perform tasks using personas, prompts, context, and tools.

8

Select a Persona for the Agent

Drag a persona from the side panel into the agent node. The persona avatar and name will fill the node prominently. This sets data.config.persona_id.

9

Add a Prompt to the Agent

Drag a prompt into the agent node to define what task the AI should perform. This sets data.config.prompt_id and loads the full prompt into the agent.

10

Add Context Blocks (Optional)

Drag context blocks into the agent node to provide relevant background information. This sets data.config.context_ids as an array.

11

Whitelist Tools - Namespaces

Drag namespace cards from the side panel into the Tools section. Namespaces show app images initially and expand to show subtools when clicked.

12

Whitelist Tools - Specific Subtools

When a subtool is selected in the builder, its full schema is loaded directly into the LLM prompt. Tools are executed via namespace wrappers with tool_name parameter.

13

Configure Node Outputs

In the Outputs section (separate from Tools), define what data this node should output for use in subsequent nodes.

14

Connect Nodes with Edges

Drag from the output handle of one node to the input handle of another to create edges. This defines the workflow execution order.

15

Add More Nodes (Optional)

Add additional agent nodes, guardrail nodes, or human approval nodes to create multi-step workflows. Use outputs from previous nodes as inputs.

16

Test Run with Current State

Click "Test Run" to execute your automation using the current in-builder (unsaved) state. Watch the execution in real-time via SSE streaming.

17

Review Test Results via SSE Events

The execution streams events (thinking, tool_call_start, tool_execution, tool_call_complete, status_change, step_completed, error) stored in automation_run_events table.

18

Save Your Automation

Click "Save" to store your automation. You will see a confirmation prompt on reload/leave if there are unsaved changes.

19

Enable Automation

Toggle the automation to "Active" to enable scheduled runs or webhook triggers.

20

Monitor Execution History

View execution history to track when your automation runs, review results, and see detailed event timelines.

Best Practices

  • Start simple and add complexity gradually
  • Test thoroughly before enabling scheduled runs
  • Use clear, specific prompts for each agent node
  • Whitelist only the tools needed for each task
  • Monitor execution history to identify and fix issues
  • Use Uru Architect to help design complex workflows

Next Step

Learn how to use Uru Architect to build automations with natural language.

Using Uru Architect