Loops Subscriber Agent with Codex
Each event is a short, well shaped run: check suppression, read the contact, take the event for what it says it is, write the properties your rules name, and usually say nothing anywhere. Most of it is precise handling of an address, a list and a couple of fields. Codex moves through record work like that quickly, which suits a template firing per event rather than on a schedule.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Hard bounce
550 5.1.1 recipient address rejected, user unknown. This is the only billing contact on the largest annual plan on the account, 18,400 USD renewing on 12 November, and two other addresses at the same domain are still receiving product mail normally. Loops shows no suppression recorded against it before today.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Loops
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Audience rules
What each kind of event means for your audience and what should follow: which contact property records a bounce, an unsubscribe or a signup, which domains and plans are worth a Slack ping, and how many departures off one send count as a run.
Runs on Codex
Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Codex for this agent
Three events, three meanings
A hard bounce means an address stopped accepting mail, an unsubscribe means a person chose, a signup means a signup. None of the three is evidence for either of the others.
Most runs end silently
Routine events are recorded and finished without a message. The channel is reserved for the customer domain and the run of departures.
Before you fork
What happens if three thousand contacts import at once?
Cost follows events, so a bulk import produces a run per contact created, and that is a spike worth expecting. Slack stays quiet because a signup is routine, but the runs still happen. If you are migrating a list, pause the workflow for the import and switch it back on afterwards.
Run it with a different agent
Put Loops Subscriber Agent to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.