
Valentina Akpan: Founder of Rellatech, providing administrative and operations support to executives, founders, business owners and teams. Her background combines technical support, customer success, administration and operations.
·
When a Keap automation stops working, there is often no alert. A campaign can stop running because a tag was renamed, a webhook can return a 404 error without anyone seeing it, or a Zap can turn off after too many errors. You often find out later, when a follow-up that should have gone out did not, and you cannot tell when it stopped.
Below is the audit I run on a Keap account before I change anything in it.
Step 1: List every active automation
- ●List every published campaign in Keap and put it in a sheet
- ●Add every active Zap that touches Keap (trigger or action)
- ●Add every webhook URL Keap calls out to
- ●For each row, note: what should trigger it, how often you expect it to run, last contact entered, last contact completed, last error
Step 2: Sort by 'days since last completion'
A campaign that has gone quiet needs a review, but that does not mean it is broken. Compare each one against the rhythm you wrote down in step 1. A welcome sequence that runs off a daily lead form and has had no entries for weeks is worth opening. A campaign tied to an annual renewal or a seasonal launch can be quiet for months and be fine. When a quiet campaign should have been busy, the cause is usually one of two things: contacts are not entering it (a tag or form problem), or people are entering and getting stuck (a sequence problem).
Step 3: Open the review candidates and check
- ●Are merge fields pointing to fields that still exist?
- ●Do 'Apply Tag' steps reference tags that still exist?
- ●Do HTTP Post URLs return a success response when you test them in Postman or a similar tool?
- ●Are sequences orphaned, with no goal pointing to them?
- ●Are contacts sitting in a wait step for longer than that step was designed to hold them? That usually means a downstream condition never resolves.
Step 4: Check the Zapier and webhook layer
- ●Open Zap History in Zapier and filter for errored and stopped runs over a recent window, such as the last 30 days
- ●Open each errored Zap and read the error message (often an expired connection or a removed field)
- ●Reconnect the Keap account inside Zapier if any Zap reports an expired or invalid connection
- ●Set up error alerting. Zapier sends its own error emails, and it has a built-in Zapier Manager app that can trigger on Zap errors. Check the current Zapier documentation for what your plan supports, then send those alerts to Slack or a shared inbox that a named person on your team checks
The most important step in this audit is setting up the error alert. In my experience, the most common reason a Keap automation stays broken is that no alert tells you it has stopped working.
Step 5: Document what's running
Keep one shared sheet listing every active campaign, its purpose, its trigger, its expected rhythm, and the last person who edited it. Update it every quarter, and name one person on your team as responsible for it. In my experience, the accounts that stay in good shape are the ones with this sheet and a clear owner.
FAQ
Help reviewing your Keap account
I help review Keap and Infusionsoft records, campaigns and integrations, then scope the corrections and documentation needed. You can find the scope and pricing on the Keap & Infusionsoft Consultant service page.
Book a free callChoose a time that suits you on the booking page. On the call, tell me what needs attention and which tools you use. Any detailed audit or implementation is scoped separately.
Related Services
Related Reading