Cap Notifications Agent

Contents

1. What the agent does
2. Reading the email
3. Thresholds
4. How lifetime caps are measured
5. What gets left out
6. How the workflow runs
7. Making changes
8. Constraints that shape the build
9. Troubleshooting

1. What the agent does

The Cap Notifications Agent sends one email every weekday morning listing partner and offer pairs that are at or over a custom cap in Everflow. It replaces the cap alert email that previously ran in Hitpath.

It runs at 12:00pm Pacific, every day, as n8n workflow CzaKa5h6VBaGRZKG on madrivo.app.n8n.cloud. Nobody triggers it.

It goes to pubteam@madrivo.com, copying angela@madrivo.com as the workflow owner.

The email is grouped by publisher manager, worst line first, so each manager can find their own section and act on it. Every partner name links straight to that pair's Pacing report in Everflow.

A companion diagram, shows the same process visually with click-through technical detail on each step.

2. Reading the email

The header strip carries five counts:

Each line shows the partner, the offer, the bizdev rep, the cap and its period, what has come through, and the percentage.

Cap mode is the field people miss. A soft cap warns but lets traffic keep flowing — that is a live situation worth acting on. A hard cap stops traffic at the limit, so a hard cap at 101% usually means the cap already did its job, and there is nothing left to do. Hard caps sitting well above 100% point at a configuration problem rather than partner overdelivery.

Colour follows severity: muted slate under 100% (approaching, not breached), then orange at 100–149%, red at 150–199%, dark red at 200% and above.

The list is capped at 35 lines so Gmail does not clip the message. When lines are held back, a banner says how many and points to the Pacing report for the full set.

A quiet day still sends an email saying nothing is over threshold. Silence would be ambiguous — you could not tell a clean day from a broken workflow.

Each cap period is listed from a different point:

Weekly and monthly sit at 85% deliberately: they are an early warning, so there is time to request a cap increase before the cap is actually hit. Daily sits at 120% because a daily cap slightly over is normal noise.

A line stays in the email day after day until the cap is raised or the partner is brought back under it. It does not show once and disappear.

A lifetime cap counts only what has come through since the cap was created — not all history.

This matters more than it sounds. Most lifetime caps were added to partner/offer pairs that had already been running for months. Counting everything back to the beginning resurfaces old volume as a permanent breach that can never be cleared. One real pair showed 157 conversions against a 125-lead cap that was created two months after that partner had already stopped sending traffic.

So the email reports "since you set this cap, they have delivered X," which is a number someone can act on.

This deliberately differs from Everflow's own Pacing report, whose "Global Cap Used" summary appears to count all time. The two will not match on lifetime caps, and that is intended.

Four filters run before anything reaches the email:

The footer of every email reports how many lines each of the first two filters removed, so nothing disappears silently.

Manager exclusions live in one list at the top of the Build Cap Email node:

const EXCLUDE_MGR = /^(Internal|Ian)\b/i;

The match is anchored to the start of the name on a word boundary, so Ian catches "Ian Ho" but not a name like "Ianthe". Adding or removing someone is a one-word edit here.

Seventeen nodes, one path, about 70 seconds end to end.

Reload the n8n tab before running a workflow manually. A manual run uploads whatever is on your browser canvas, not the saved server copy. A stale tab will run an older version, and the editor can autosave that stale canvas over newer work.

Two platform limits explain most of how this workflow is put together. Both are easy to reintroduce by accident.

n8n keeps every node's output in memory for the whole run. Peak memory is the sum of everything the run has touched, not the largest single item. So every Everflow query is scoped by offer and partner ID to the pairs that actually carry a cap of that period — never network-wide.

A period with no caps still has to filter to something. An empty filter array means no filter, which silently becomes a network-wide query. Empty scopes fall back to offer ID 0, which matches nothing.

Do not add ?relationship=all to the capstable request. It attaches full offer and partner objects to every one of tens of thousands of records. Names come from the report rows instead, which already carry them.

Everflow rate-limits bursts of API calls, and n8n passes the failures through quietly. The lifetime query groups by month so a single request covers a whole year, keeping the run to about five lifetime calls. Both lifetime nodes retry three times, three seconds apart, and anything still missing is counted and surfaced as a banner in the email rather than reported as zero.

Click caps are measured on unique billable clicks, not gross. Everflow enforces them that way — confirmed on a live offer where two partners stopped at exactly their 1,500-click cap while gross traffic ran to roughly double, the excess landing in Invalid Clicks. Because the lifetime query filters on conversions, click caps need the separate Lifetime Clicks pass or a partner burning clicks without converting would be invisible.

Article Owner: Angela Jimenez

Written By: Angela Jimenez

Date Last Modified: September 17, 2026

Tags: Everflow, n8n, Operations, PDM Caps, Automation, Reporting, Agent, AI