Running Automations
Automations run in three ways: manual (on demand), scheduled (time-based), or event-driven (when something happens). The trigger type you add in the Build tab determines how the automation runs.
Manual Execution
- Open the automation and go to the Run tab
- Enter values for any required inputs (defined by the Manual Trigger)
- Click Run
- Watch progress: the current step is highlighted; outputs appear as each step completes
- Expand step outputs to view JSON or copy data
Use case: Testing, one-off runs, user-initiated processes.
Scheduled Execution
- Add a Scheduled Trigger as the first step in the Build tab
- Configure the schedule:
- Frequency – Hourly, daily, weekly, monthly, or custom cron
- Timezone – When the schedule runs
- Time – Specific time for daily/weekly/monthly
- Use the Schedule toggle in the Build tab toolbar to enable or disable
- Use Manage → Manage Schedule to view all scheduled automations, enable/disable, edit, and see last/next execution
Use case: Daily reports, weekly syncs, monthly billing.
Event-Driven Triggers
These fire in real time when an event occurs:
- Slack Channel Message – Message posted in a channel; configure channel(s) and optional filters
- Slack Direct Message – DM received
Configuration: Set the channel, optional text filter, and optional user filter in the trigger step.
Use case: Auto-respond to Slack, create tasks from messages.
Polling Triggers
These check external systems periodically and run when new data matches:
- HubSpot – Contact/Company/Deal Created
- Gmail – New Email, Email Sent, Email Archived
- Office365 – New Email, Calendar Event Created, Meeting Starting/Ended
- Google Calendar – Event Created, Meeting Starting/Ended
- Google Drive – File/Folder Added
- Google Sheets – New Row
- Airtable – New Record
- Todoist – Task Created
- Fireflies / Avoma – Transcript Available
Use case: Process new HubSpot contacts, react to new Gmail, run when meeting ends.
Execution States
- Not Started – Ready to run
- Running – In progress; current step highlighted
- Completed – Finished successfully
- Failed – Error occurred; check step outputs for details
- Cancelled – Stopped by user
Viewing Outputs
In the Run tab during or after execution:
- Each step has an expand/collapse control
- Expanded steps show output as JSON
- Copy or use outputs for debugging
- Outputs from one run are available until you run again
Batch Runs
In the Batch tab:
- Add rows – Manually enter inputs for multiple runs
- Import CSV – Load inputs from a CSV file
- AI Import – Upload a document; AI extracts input rows
- Run All – Execute all rows
- Run Selected – Run only selected rows
Use batch runs when you have many input sets (e.g., multiple contacts, deals, or documents).
History
The History tab lists past runs:
- Columns: Run ID, status, creator, start/end time
- Filter by status, date range, creator
- Click a run to view full details and step outputs
- Re-run – Start a new run with the same inputs (if supported)
Managing Schedules
Go to Manage → Manage Schedule to:
- View all scheduled automations
- Enable or disable individual schedules
- Edit schedule configuration (frequency, timezone, time)
- See last execution and next scheduled execution