> ## Documentation Index > Fetch the complete documentation index at: https://docs.agentova.ai/llms.txt > Use this file to discover all available pages before exploring further. # Actions & search > Pause or reactivate an automation from a Zap, and find it by name ## Activate Automation and Pause Automation **Activate Automation** turns a paused automation back on; **Pause Automation** pauses an active one. Both have a single field: | Field | What to put | | - | - | | **Automation** | Pick the automation in the list, or map its ID (`aut_…`) from a previous step — for example the result of a **Find Automation** step. | ![The event list of an Agentova action step in Zapier: Activate Automation and Pause Automation under Create, Find Automation under Search](https://mintcdn.com/agentova-2c667f5d/Xl6jEAYNYyd4kO2m/images/zapier/action-events.jpg?fit=max\&auto=format\&n=Xl6jEAYNYyd4kO2m\&q=85\&s=0dc78cd361a6def0958c70b053362104) Agentova's actions and search, when choosing the event of an action step The step returns the automation with its status **after** the change. If Agentova couldn't apply the status — for example, the automation couldn't be reactivated and is now in error — the step fails with a message saying so, instead of showing a success. Pausing and reactivating are **safe to repeat**: pausing an automation that's already paused, or activating one that's already active, returns it unchanged — no error, and no new status event. The API answers within **8 seconds**. When reactivating takes longer — reconnecting a mailbox, for example — the response shows the status at that moment, and the final status arrives as an **Automation status changed** event: `active`, or `error` if the channel couldn't be reconnected. Nothing that arrives during a pause is caught up afterwards, except for Customer.io after a short pause: | Channel | While paused | When reactivated | | - | - | - | | Emails (Gmail, Outlook, IMAP) | Agentova stops listening to the mailbox — unless another active agent uses the same mailbox. Emails received during the pause **get no reply**. | The mailbox is reconnected. Only the emails that arrive from then on are handled. | | Private messages (Facebook, Instagram, WhatsApp), comments, stories | Whatever arrives is ignored | New messages, comments and story replies are handled again | | Lead Ads | Leads are still saved in Agentova and announced by **Lead created**; only the automation's actions (message, email, call…) are skipped | Actions run again for new leads; the skipped ones are not run afterwards | | CRM sources | Agentova stops reacting to the CRM | Events that happened during the pause are not replayed | | Customer.io | Agentova stops reading the segment (it normally reads it every 15 minutes) | After a pause of more than 6 hours, the segment changes made during the pause are never handled; after a shorter pause, they may be handled when the automation resumes | Only `active` and `paused` automations can be switched. A `draft` or `error` automation is refused (`422 automation_not_controllable`): fix it in the Agentova app first. A mailbox can only be used by one active agent, as in the Agentova app: reactivating an email automation whose mailbox another active agent already uses is refused too (`422 automation_not_controllable`, with `details.reason: account_in_use`). Detach the mailbox from the other agent in the Agentova app first. ## Find Automation Finds an automation so that a later step can use it. | Field | What to put | | - | - | | **Automation** | Pick the automation in the list, or map its ID from a previous step. When it's set, **Name** is ignored. | | **Name** | The automation's name. An exact match (case doesn't matter) comes first; otherwise, the most recently created automation whose name contains the text. | Automation names read “*what the automation does* — *agent name*”, for example “Comment replies — Support Agent”, “Email replies — Support Agent” or “Lead Ads — Support Agent”, and for a CRM source “HubSpot contacts — Support Agent”. The names of messaging automations don't contain the channel, so searching “Instagram” finds nothing. And the same agent on two channels gives two automations with the same name. > [!TIP] > > To always reach the same automation, **pick it in the list or use its ID**. If you search by name, copy the exact name from the Agentova app. ## Errors you might see | Message | Why | What to do | | - | - | - | | “Automation not found in this Agentova workspace…” | The automation was deleted or turned off in Agentova, its account was disconnected, or it belongs to another workspace | Pick the automation again in the list | | “This automation is a draft…” or “This automation is in error…” | Drafts and automations in error can't be switched from a Zap | Fix the automation in the Agentova app, then retry | | “This mailbox is already used by another active Agentova agent…” | Another active agent already uses the mailbox of this email automation: Agentova allows one active agent per mailbox | Detach the mailbox from the other agent in the Agentova app, then retry | | “Agentova couldn't activate this automation: it is now in error…” | The automation couldn't be reactivated, for example because its connection couldn't be restored | Check the automation's connection in the Agentova app | | “Agentova's request limit was reached…” | More than about 100 requests per minute with this key | Nothing: Zapier retries automatically after the delay | | “Invalid or revoked API key…” | The key used by this account was revoked | Reconnect the account with a new key | | “The Agentova API is temporarily unavailable…” | Agentova switched its API off for a while | Retry later | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.