Most "my agent is not working" cases are one of six things: it is still a Draft, the trigger did not fire, the goal is too vague, a stage or field it needs does not exist, the credit pool is empty, or the webhook payload does not match the goal. Work down this list.
Open the Agents tab. The Status column must say Running. A Draft has never been activated and will not fire, no matter what triggers it has. A Paused agent was stopped by someone. Open the agent and click Activate.
Check Last Execution in the list and the Activity tab on the agent. No run at all means the event never reached the agent.
New Company only fires for companies created after activation. Existing records need Enroll Agent or an Action Bar run.
Deal Updated fires on deal changes, not company changes. If you edited a company field, nothing happens.
Webhook: the sending tool must POST JSON to the exact URL from the Webhook tab, and the Webhook toggle must be on. Send a test from Make, Zapier or n8n and watch Activity. Nothing within a minute means the request is not arriving: wrong URL, wrong method, or the scenario is off.
No triggers at all: the agent is on-demand only. That is fine if you intended it; otherwise add one.
Open the run in Activity and read the log. Common causes:
The goal did not say what to do for this record, so the agent stopped. Add an explicit "if ... then ..." for the case.
A scope condition excluded it ("only companies from the website form") and the record did not match. That is the agent working as written.
The goal asked for review ("draft and leave for me"), so the message is waiting for you on the record, not sent.
The AI Analyzer saw a reply, click or booked meeting and stopped the sequence. Check the record timeline.
The error names the step. Check:
Stage names: "Demo booked" and "Demo Booked" are different. Match Pipelines exactly.
Custom fields: the field must exist in Settings → Custom Fields for the right object. A deal field will not work on a company.
Email steps need a connected mailbox in Settings → Connected Apps. SMS steps need a K3X number with approved registration in Phone & Voicemail.
Webhook-out steps need a public HTTPS URL. See Deliveries for the response.
Agent runs are paid actions. When the pool hits zero, the CRM keeps working but runs pause. Click your avatar and look at Usage this cycle, or open Settings → Billing. Add a top-up pack or turn on Auto-recharge; paused runs resume once credits are available.
If a webhook run fails on the first step, the goal is probably referring to a field the payload does not contain. Look at the real payload in the run log, then use those exact key names in the goal. Nested objects are harder to reference than flat keys, so flatten in Make, Zapier or n8n before sending.
Pause the agent so it stops spending.
Enroll it on one test record and read the run.
Share the agent name and the run time with support: [email protected] or the SUPPORT chat bubble at the bottom right. We take runaway-agent reports seriously.
Monitor agents: Activity, Deliveries, errors, success rate and credits
Webhook-triggered agents
Steps and the AI Analyzer
Getting help: support, demos and onboarding
