Creating Automations

Create automations using AI generation, from scratch, or from a template. Use the Build tab to add steps, configure inputs, and wire outputs between steps using variables.

Creation Methods

Generate with AI

Best when you have a clear idea of what you want. Be specific and mention integrations or timing.

1. Click Create New Automation
2. Select Generate Automation with AI
3. Enter a detailed description (e.g., “Send a follow-up email 3 days after a customer makes a purchase”, “Create a daily sales report automation”)
4. Click Generate with AI
5. Wait for AI generation (progress indicator)
6. Review the generated steps, name, description, and category
7. Customize name, description, category, and step configs as needed
8. Click Create Automation
9. The automation opens in the Build tab

AI generation tips: Mention integrations you want, specify timing (daily, when X happens), and include desired output format or destination.

Create from Scratch

Best for full control. You add every step yourself.

1. Click Create New Automation
2. Select Create Automation from Scratch
3. Enter name and description
4. Select a category (optional)
5. Click Create Automation
6. The automation opens in the Build tab with an empty canvas
7. Add a trigger as the first step, then add action steps

Start from Template

Best for common patterns. Templates are grouped by category.

1. Click Create New Automation
2. Select Start from a Template
3. Browse template cards (name, description, category, steps preview)
4. Click a template to select it
5. Click Use Template or Continue
6. Customize name, description, and category
7. Click Create Automation
8. The automation opens with template steps pre-configured

Build Tab

The Build tab is where you design the automation.

Layout

• Toolbar – Schedule toggle (for scheduled automations), error summary
• Steps canvas – Steps shown in execution order
• Add Step button – Add new steps

Step Display

Each step appears as a card with:

• Step name and type icon
• Input summary (if configured)
• Error indicators (if validation fails)
• Edit, Delete, Duplicate, Move Up/Down buttons

Adding Steps

1. Click Add Step
2. In the dialog, browse Triggers, Actions, and Logic
3. Select a step type
4. The step is added; the configuration dialog opens
5. Fill in required inputs and save

Trigger must be the first step. Add actions and logic steps after it.

Editing Steps

• Click Edit on a step card, or click the card
• The step configuration dialog has:
  • Header – Step name (editable) and type icon
  • Inputs – All configurable fields
  • Advanced options – Collapsible extra settings
  • Output schema – Preview of outputs for use in variables

Step Input Types

• Text – Single-line or multi-line; supports variables
• Dropdown – Single-select from options
• Multi-select – Multiple selections
• Date picker – Calendar date
• Time picker – Time of day
• Number – Numeric with optional min/max
• Checkbox – Boolean
• File upload – Attach files
• External data provider – Select from HubSpot, Google Drive, etc.
• Variable editor – Rich text with #variable# support

Variables in Inputs

In variable-enabled fields:

• Type # to open the variable menu
• Browse Input Variables (from trigger), Step Outputs (from previous steps)
• Use field access: #StepName.fieldName#
• Use array access: #StepName[0]# or #StepName[0].fieldName#
• Select to insert; the reference is inserted as #variableName#

Output Schemas

Steps produce outputs. View them in the Output Schema section of the step dialog. Use outputs as variables in later steps (e.g., #GenerateText.output#).

Validation

• Required inputs are marked with *
• Invalid inputs show error messages
• Automation-level errors appear in the toolbar error summary
• Step cards show error indicators

Step Actions

• Edit – Open configuration
• Delete – Remove the step
• Duplicate – Copy the step
• Move Up / Move Down – Reorder steps

Best Practices

• Use AI generation for quick drafts, then refine
• Mention integrations and timing in AI prompts
• Test with manual runs before enabling schedules
• Use variables to chain steps instead of hardcoding values
• Check the error summary and fix issues before saving