One rule, one assignee
Name the outcome, write instructions, and assign an Agent or Crew. Active or Paused is the only status the rule needs.
SharklyAutomations
Recurring work should notwait for someone to poke it
An Automation is one rule: instructions, an Agent or Crew, triggers, and run history. It can start a run directly, or create a Task and have an Agent execute it.
Used by teams at
Rule, trigger, review
Automate the repeat. Keep people on review.
Use an Automation when the same well-defined work should start on a schedule or event. Keep the history on the rule. Use a Task when the request needs an owner.
Start from events you already have
Schedule, task status, comment phrase, webhook, or a manual start. Triggers can be enabled independently on the same Automation.
Land the work on a Task
An Automation can create the Task, assign an Agent, and keep the result on the board. People review the same record they already use.
Rule, trigger, review
Write the rule. Let the event start it.
An Automation is one Agent or Crew rule: instructions, triggers, and run history. It can start a run on the rule, 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. People still review what matters.
- 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 a run can start
Schedule uses cron and a timezone. Status and comment triggers listen for events. Webhooks accept a signed POST. 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. Let the Agent execute it.
An Automation can open a Task, assign an Agent, and run the work on that record. Recurring briefs and similar jobs land on the board with owner, status, and the 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, who runs, where history lives
Use an Automation to start the repeating work. Use a Task when that work should land on the board for people to own and review.
Schedule
Cron plus timezone for checks, summaries, reminders, and maintenance.
Task status
Starts when a Task moves into a selected organization status. Matching is currently organization-wide.
Comment phrase
Starts when a comment contains a configured phrase. Matching is also currently organization-wide.
Trigger from the tools you already run
Webhooks in. Slack and Jira nearby.
Inbound webhooks start Automations. Slack and Jira still create or sync Tasks that people and Agents can then run.
JiraGitHubSlack
Connected features
Automations are not a second Task system
When the request needs an owner, put it on a Task. An Automation can create that Task and run it, or keep history on the rule.
Quality of life, built in
The details that keep recurring work reviewable
A run that nobody can find is worse than work that waited for a person.
Run history on the Automation, or a Task the team can review
Triggers that can be enabled independently
Create a Task and assign an Agent so the work executes on the board
Webhook URLs shown once, with optional signing secrets
Honest organization-wide matching for status and comment triggers today
Manual start when you need a run without waiting for an event
Let the repeating work start itself
Write the instructions, assign an Agent or Crew, and attach the triggers you already trust.