Automation

Automation in ACP connects threads, projects, and resources to time-based and event-based triggers. This is how recurring work and external system integrations become first-class.

Automation

Use schedules and webhooks to trigger ACP work from time or external events.

What automation means in ACP

ACP automation is built around schedules and webhooks. Schedules let you run recurring work on time-based triggers, while webhooks let external systems start ACP logic in response to real events.

Run recurring reporting, briefings, syncs, and maintenance tasks.

Connect third-party systems to ACP threads and project workflows.

Keep automation inside the same execution model as manual work.

Schedules

Schedules let ACP run work continuously or on a cadence. A scheduled run uses the same agent, project, and computer model as an interactive run, which makes recurring automation easier to reason about.

Use schedules for recurring threads and project tasks.

Keep recurring work inside the same execution and audit model.

Tie automation to real project resources and computers.

Webhooks

Webhooks let ACP react to external events from products, backends, or enterprise systems. That turns ACP into an event-driven execution layer instead of a purely interactive UI.

Trigger work from product events or operational systems.

Connect inbound events to projects, threads, and resource workflows.

Use ACP as the control plane behind event-driven automation.