My Zap doesn’t trigger
Is the Zap published and on?
Is the Zap published and on?
Instant triggers only work on a published Zap that is on. Testing in the editor doesn’t register anything with Agentova.
Does the event really happen for this workspace?
Does the event really happen for this workspace?
- New Lead: 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. See Triggers.
- 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.
Did the Zap stop receiving events after an outage?
Did the Zap stop receiving events after an outage?
If Zapier couldn’t receive events for a long time, Agentova makes up to 8 delivery attempts for each one over about 27 and a half hours. Once three in a row have been abandoned and deliveries have been failing for at least 72 hours, Agentova stops notifying that Zap and alerts your workspace admins. Turn the Zap off and on to register again.
Was Agentova's API switched off?
Was Agentova's API switched off?
Agentova can switch its API off for a while. The events that happen during such a break are never delivered to your Zaps.
Was its registration deleted in Agentova?
Was its registration deleted in Agentova?
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. If the Zap’s subscription was deleted, reconnect the account with a valid key if needed, then turn the Zap off and on to register again.
A run shows as “Halted”
That’s the app protecting your Zap, not an error:- “Ignored a repeated delivery…”: Agentova sent the same event again after a network problem, and the app recognized it.
- An unsigned or forged notification, or one signed more than an hour ago, is ignored too.
The Test trigger step finds nothing
It shows your most recent real items. A new workspace has no lead or run yet: create a lead through your chatbot’s contact form, or wait for an automation to run, then test again.An action fails
Limits
- About 100 requests per minute per API key. Zapier waits and retries on its own if you go over.
- 20 active subscriptions per workspace: each published Zap with an Agentova trigger uses one, as do other tools such as n8n.
- 10 active API keys per workspace.