Migrate from Agents
How to move discontinued agents to Automation
Agents have been discontinued and replaced by Automation. What agents did — analyzing data, creating reports, delivering them by email or Slack, and running via the API — Automation does too. Existing agents can be moved to Automation with a single button.
Existing agents no longer run, and their schedules no longer fire. Reports your agents used to send stop arriving until you migrate.
Migrating
Open the Agents tab
Open the project's Agents tab. A notice at the top of the list reads Agents have been discontinued.
Click "Move to Automation"
A new chat opens, and the AI turns each agent in the project into an Automation, one at a time.
Each agent's name, schedule, and notification destinations carry over.
Review the migrated Automations
When migration finishes, the chat shows a summary. The migrated Automations appear as cards in the editor's Project tab.
Open each one, click Run now, and check that the report arrives as expected.
Migrating does not delete the original agents. Their settings and past run history remain available in the Agents tab. Clicking Move to Automation again does not create duplicates for agents that were already migrated.
What changes
| Agents | Automation | |
|---|---|---|
| How you create it | Chat and forms | Chat |
| How you change it | Forms or chat | Chat |
| On failure | — | Can notify only when something fails |
| Run history | The result of each run | Results and credits for each step |
| Running via the API | /agent/{agentId}/trigger | /automation/{projectId}/{automationName}/trigger (Run via the API) |
| Email recipients | Any address | Project members only |
| Credit usage | Based on AI usage | Based on the kind of step (Automation credit usage) |