Automations

Start repeatable agent work from a trusted event.

Planned automations pair clear instructions with an agent or crew, one or more triggers, and an inspectable run history. They accelerate repetition without automating the team’s final judgment.

Pre-release noteAutomations are part of the proposed launch scope and are not active on this marketing website.

Request early access Discuss your use case

Trigger from schedule, status, comment, or webhook

Use an event your team understands to begin a narrow task such as a standup digest, first-pass bug analysis, documentation check, or release report.

↗Pause a rule without deleting its history
↗Record the trigger, result, and failure reason
↗Use a task when the work needs an owner and board status

Prefer explicit boundaries to broad autonomy

Each automation should name the sources it may read, the actions it may take, the expected output, and when it must ask a person. Secrets and webhook URLs require controlled handling.

Keep review where the result matters

A direct run can retain history on the rule. Work that changes a product or process should create or update a task so a person can inspect and accept the result.

Pre-release · No instant signup or payment

See whether M1 Project fits your team’s operating model.

Request a walkthrough