Skip to main content

​
The trigger never fires

Only an active workflow is registered with Agentova. A saved but inactive workflow receives nothing (except while you click Listen for test event).
Your instance must be reachable from the internet over HTTPS, at the address set in n8n’s WEBHOOK_URL. localhost, private network addresses and plain http:// are refused by Agentova. For a local test, a tunnel (Cloudflare Tunnel, ngrok…) giving a public HTTPS address works.
  • Lead Created: only the chatbot contact form, Lead Ads, phone calls, prospects who send their contact details after commenting a post, and incoming CRM contacts create leads. A private message or an email your agent replies to doesn’t.
  • Run Completed: CRM sources other than Customer.io (HubSpot, Typeform, Close…) produce runs only when the workspace has a single such CRM automation.
  • Automation Status Changed: pausing an automation that’s already paused changes nothing, so nothing fires. Deleting an automation or turning it off in the Agentova app doesn’t fire either.
Once three deliveries in a row have been abandoned — each after up to 8 attempts over about 27 and a half hours — and deliveries have been failing for at least 72 hours, Agentova disables the subscription and alerts your workspace admins. Deactivate, then activate the workflow: the trigger replaces the disabled subscription.
The events that happen while the API is switched off are never delivered. Once it answers again, catch up with the API’s list endpoints (GET /leads, GET /runs, or Agentova → List for automations).
Workspace admins can delete webhook subscriptions in Paramètres → API (Settings → API). Revoking a key also deletes, by default, the subscriptions created with it — and a key is revoked automatically when the admin who created it leaves the workspace or stops being an admin. Update the credential with a valid key if needed, then deactivate, then activate the workflow to register again.

​
“Agentova Trigger: rejected a webhook delivery” in the n8n logs

The reason says why the notification was refused:

​
The same event ran twice

The trigger’s memory of processed events lives in the n8n process: a restart, or several n8n instances in queue mode, can let a repeated delivery through. Add a Remove Duplicates node after the trigger, as shown in Agentova Trigger.

​
Activate fails on an email automation

“This mailbox is already used by another active Agentova agent”: a mailbox can only be used by one active agent, as in the Agentova app. Detach the mailbox from the other agent in the Agentova app, then run the node again.

​
“The Agentova API is temporarily unavailable”

Agentova switched its API off for a while. Retry later; to keep the workflow going, turn on the node’s Retry On Fail setting.

​
The node can’t find my automation

  • It was deleted or turned off in the Agentova app, or its account was disconnected: such automations don’t appear.
  • It belongs to another workspace: check which credential the node uses.
  • It’s a phone agent or the website chatbot: those aren’t automations in the API.

​
Limits

  • About 100 requests per minute per API key, shared by every workflow using it.
  • 20 active subscriptions per workspace: each active workflow with an Agentova Trigger uses one, as do other tools such as Zapier.
  • 10 active API keys per workspace.