> ## 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. # Agentova node > List, get, activate and pause your automations from a workflow Resource: **Automation**. Four operations. ## List Returns the automations of the workspace, one item per automation. | Option | What it does | | - | - | | **Return All** | Fetches every page, 100 automations per request. Off: stops at **Limit** (50 by default). | | **Filters → Status** | `Active`, `Paused`, `Draft` or `Error` | | **Filters → Type** | One automation type (see below) | | **Filters → Agent ID** | Only the automations of one agent (`agt_…`) | Each item contains: `id`, `name`, `type`, `provider`, `agent_id`, `agent_name`, `status`, `updated_at`. ![The List automations node in n8n: credential, Automation resource, List operation, limit 50, and four automations in the output with their ID and name](https://mintcdn.com/agentova-2c667f5d/Xl6jEAYNYyd4kO2m/images/n8n/list-automations.jpg?fit=max\&auto=format\&n=Xl6jEAYNYyd4kO2m\&q=85\&s=b2031cdd7c388bef4d5c3d0a8d9bce98) List run from a manual trigger: one row per automation | Type | What it does | Channels (`provider`) | | - | - | - | | `social_comments` | Replies to comments on your posts | Facebook, Instagram | | `social_story` | Replies to story replies | Instagram | | `social_messages` | Replies to private messages | Facebook, Instagram, WhatsApp | | `lead_ads` | Handles Lead Ads forms (message to the prospect, add to your CRM) | Facebook, Instagram | | `email_messages` | Replies to emails | Gmail, Outlook, IMAP | | `crm_source` | Acts when a contact or a response arrives in a CRM or a form tool | HubSpot, Close, Monday, ClickUp, Typeform, Tally, Odoo, Customer.io… | **Not covered in v1:** phone agents, the website chatbot itself (it's an agent, not an automation), scheduled social posts, and builder workflows. An automation that was deleted or turned off in the Agentova app, or whose account is disconnected, doesn't appear at all. ## Get Returns one automation. Choose it in the **Automation** field: * **From List**: a searchable list of your automations — type part of the name. * **ID**: paste an ID (`aut_…`), or map it from a previous node with an expression such as `{{ $json.id }}`. Automation names read “*what the automation does* — *agent name*”, for example “Comment replies — Support Agent”, “Email replies — Support Agent” or, for a CRM source, “HubSpot contacts — Support Agent”. The same agent on two channels gives two automations with the same name: when two lines look alike in **From List**, use the **ID** mode. ## Activate and Pause Switch one automation to `active` or `paused`. The **Automation** field works like in **Get**. The node returns the automation with its status after the change. If Agentova can't restart the automation — for example a CRM source whose connection can't be restored — the automation ends up in `error`, and **Activate** fails with “Automation “…” could not be resumed, now in error” instead of reporting 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. ## Use it as a tool for an AI agent The Agentova node can be connected as a **tool** to n8n's **AI Agent** node. The agent can then list your automations, look one up, and pause or reactivate it when you ask in plain language — for example “pause the comment replies”. It doesn't schedule anything by itself: reactivate later by asking again, or with a scheduled workflow. > [!WARNING] > > An AI agent with this tool can pause any automation of the workspace. Give it a clear system message about what it may and may not do. ## Errors The node picks its message from the error `code` returned by Agentova: | Message in n8n | Why | What to do | | - | - | - | | “Automation not found” | The automation was deleted or turned off in Agentova, its account was disconnected, or it belongs to another workspace | Pick the automation again **From List** | | “This automation cannot be controlled through the API” | The automation is `draft` or `error` | Fix it in the Agentova app first | | “This mailbox is already used by another active Agentova agent” | **Activate** on an email automation whose mailbox another active agent already uses: a mailbox can only be used by one active agent | Detach the mailbox from the other agent in the Agentova app, then retry | | “Invalid or revoked Agentova API key” | The key was revoked or is wrong | Update the credential | | “This Agentova workspace has no access to the API” | The workspace's subscription is unpaid, paused or incomplete | Check **Paramètres → Abonnement** (the plan) or **Paramètres → Facturation** (payment method, invoices) | | “Agentova rate limit reached, retry in … s” | More than about 100 requests per minute with this key, all workflows included | Slow the workflow down (Wait node, smaller batches) | | “Agentova API route not found” | The Base URL of the credential is wrong | Set it back to `https://core-api.agentova.ai/v1` | | “Agentova internal error” | A temporary problem on Agentova's side | Retry later; [contact support](https://docs.agentova.ai/en/support.md) if it persists | | “The Agentova API is temporarily unavailable” | Agentova switched its API off for a while | Retry later | To keep a workflow running when one item fails, turn on the node's **On Error → Continue** setting. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.