What an agent will not do without you
A connected agent can build and run most of the business, but a few things stay with a person by design: uploading and running CSV imports, enrolling contacts in Reply.io sequences, exporting a collection, replaying runs that call an AI model, and sending an email without your confirmation. It also never sees secret fields and never exceeds your role.
A connected agent can build and run most of the business, but a few things stay with a person by design: uploading and running CSV imports, enrolling contacts in Reply.io sequences, exporting a collection, replaying runs that call an AI model, and sending an email without your confirmation. It also never sees secret fields and never exceeds your role.
Requirements
None to read. For connecting an agent, see Connect to the MCP server.
What stays with a person
| Action | What the agent does instead | Why |
|---|---|---|
| CSV import | Prepares the column mapping as a reusable preset | Uploading a file and writing hundreds of entries is a deliberate human act. See Import entries from CSV. |
| Enrolling in Reply.io sequences | Reads which sequences a contact is in | Enrolling starts outreach to real people. See Enroll contacts in a Reply.io sequence. |
| Exporting a collection | Points you to the collection's own export | Every exported row carries the entry's internal id. |
| Replaying a run with an AI step | Checks the automation with a dry run, then asks you to run it | Each AI call can cost money at your provider. See Inspect an automation run. |
| Sending an email | Drafts it and confirms the content with you first | A sent email cannot be taken back. See Send an email. |
What an agent never gets
- More than your role. It acts as you, with your permissions, in one business at a time. See How an agent connects.
- Secret fields. Values declared secret are never included in what AI and integrations see; password fields are never returned to anyone. See Fields: built-in and your own.
- Entries you cannot see. Record-level visibility applies to the agent exactly as to you. See Who sees which entries.
Notes and limitations
- These are defaults of the agent's recipes and of the system. Your assistant may add its own confirmations on top, such as asking before any change.
- An agent can still do the work around these actions: prepare, check, and explain. The last step is yours.
Related
For what an agent can do, see What the tools cover and Workflow recipes for agents.