One rule, one assignee
Name the outcome, write the instructions, and assign an Agent or Crew. A rule has two states: active or paused.
HiFoxAutomations
Repeating work, handled automaticallynot on a nudge
An Automation is one rule: instructions, an Agent or Crew, triggers, and run history. It can start a run directly, or create a Task for an Agent to execute.
How it works
Agents get triggered and do the work
Use an Automation when the same well-defined work should start on a schedule or an event, and keep the history on the rule. Use a Task when the work needs an owner.
Start from events you already have
Schedule, task status, comment phrase, webhook, or a manual start. Triggers on the same Automation are enabled independently.
Land the work on a Task
An Automation can create the Task and assign an Agent, so the result lands on the board the team already reviews.
Automation Workflow
Write the rule. Let the event start it.
An Automation is one rule for an Agent or Crew: instructions, triggers, and run history. It can start a run directly, or create a Task and execute it.
01Automation
Write the rule once, keep the history on it
An Automation stores name, instructions, Space, assignee, priority, status, triggers, and run history. The steps that need judgement stay with people.
- Assign one Agent or Crew to perform the work
- Pause the Automation without deleting its history
- Inspect source, result, Agent run, and failure reason on each execution
02Triggers
Five ways to start an Automation
Schedule uses cron and a timezone. Status and comment triggers listen for events. Webhooks accept a signed request. Manual start is always available.
- Hourly, daily, weekday, weekly, or custom cron
- Comment phrases match case-insensitively anywhere in the comment
- Webhook URLs are shown once; store them and regenerate if exposed
03Tasks
Create the Task automatically. Run it automatically.
An Automation can open a Task and assign an Agent, so the work runs on that record. A recurring brief lands on the board with owner, status, and result attached.
- Create a Task from the Automation instead of a private run
- Assign an Agent so execution starts on that Task
- Keep title, description, status, and the run where the team already reviews
The automation system
What starts it, who runs it, where history lives
Repeating work is started by an Automation. Work that should land on the board for people to own and review belongs on a Task.
Schedule
Cron plus timezone for checks, summaries, reminders, and maintenance.
Task status
Starts when a Task moves into a selected status. Matching is currently organization-wide.
Comment phrase
Starts when a comment contains a configured phrase. Matching is also currently organization-wide.
Webhook
An entry point for external events, with optional signing secrets.
Run history
Stays on the Automation, or attaches to the Task it created.
Inbox
Results grouped one row per Automation and delivered to the recipients.
Connected features
Automations are not a second Task system
Put work that needs an owner on a Task. An Automation can create and run that Task, or keep the history on the rule.
Quality of life, built in
Recurring work stays reviewable
A run nobody can find afterwards is worse than work that waited for a person.
Run history on the Automation, or on a Task the team can review
Triggers that are enabled independently
Create a Task and assign an Agent so the work runs on the board
Webhook URLs shown once, with optional signing secrets
Status and comment triggers match organization-wide, and the UI says so
Manual start when you need a run without waiting for an event
Let repeating work start on its own
Write the instructions, assign an Agent or Crew, and attach the triggers.