n-Keap's Campaign Builder Can Run a Sequence. It Can't See Past Keap to Decide What To Do Next.
Keap's Campaign Builder is the drag-and-drop canvas, carried over from the Infusionsoft days and updated since, where you string together action sets (email, wait, apply a tag, assign a task) and decision diamonds that branch based on what a contact does. It's a genuinely capable way to build a sequence. What it can't do is branch on anything that hasn't already made its way into Keap as a tag or a field, which is exactly the limit we build around.
What the Campaign Builder actually does
A campaign is a canvas of action sets connected by lines and, where the logic needs to branch, decision diamonds. An action set is a small bundle of steps, send this email, wait two days, apply that tag, notify a rep, and a decision diamond checks a condition, did they open the last email, do they have a certain tag, and routes the contact down one path or the other depending on the answer.
If your account goes back to the Infusionsoft era, you may remember an older version of this canvas. Keap has continued to update the builder's interface since the rebrand, which is why searches for the newer layout show up alongside tutorials written against the older one. The underlying idea, action sets and decision diamonds strung together on a canvas, hasn't changed.
Campaigns also carry goals, the specific finish lines a contact can hit that move them into the next stage of logic, which is how Keap avoids forcing every contact through the exact same linear path regardless of what they actually do.
Where a decision diamond runs out of information
A decision diamond is only as smart as the data already sitting on the contact record. It can check a tag, a custom field, an email open, anything Keap itself tracked. It can't check whether an invoice got paid in your accounting system, whether a support ticket is still open, or whether a signed contract actually came back, because none of that exists inside Keap unless something put it there first.
That's the gap behind searches like keap webhooks: people reaching for a way to get outside events into Keap in real time rather than waiting on someone to notice and tag the contact by hand. A webhook can do that, but turning it into a tag or field a decision diamond can actually branch on, correctly and without race conditions when two things happen close together, is the part that takes real build work.
What We Build Around the Campaign Builder
Feeding the diamond real data before it has to decide
We push the outside event, a payment, a support status, a signed contract, into Keap as a tag or field the moment it happens, so a decision diamond is branching on what actually happened instead of on a tag someone remembered to add two days later.
Letting an action set finish outside Keap
A campaign step doesn't have to end at another Keap action. We wire the end of an action set to create a record, start a project, or notify a system outside Keap, so the campaign's last step is a real handoff instead of a dead end at the edge of the platform.
Got a decision diamond that needs to check something Keap can't see?
Tell us what the branch is supposed to depend on and where that answer actually lives right now. We'll tell you honestly what it takes to get it in front of that diamond in time to matter.
Running campaigns in Keap that branch on data Keap never gets to see?
Tell us which step in the campaign is guessing instead of knowing, and what the real answer depends on. We'll map out what can feed into Keap automatically before that decision diamond fires. The Campaign Builder happens to be the tool in front of you, but the same gap shows up in plenty of other systems too, and we close it the same way regardless of which one it is.
Let's talk