Loops Subscriber Agent with Claude Code

Rule one is a stop. Read the suppression state for the address before any judgement and before any write, because a contact Loops has already suppressed is closed business and working around that is neither available nor the agent's decision. Everything else in the run happens after that check clears, and Claude Code opens what it was handed before touching a field.
Loading preview…
Free to start · guided setup · switch agents any time.

Live demo

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

finance@meridian-clinics.co.zaBilling Notices

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.

What you'll need

Set up in minutes

Using this template drops you into a guided setup. It asks exactly this, nothing else:

  1. Connect Loops

    One sign-in. The agent acts through your account, scoped to what this template uses.

  2. Connect Slack

    One sign-in. The agent acts through your account, scoped to what this template uses.

  3. 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.

  4. Runs on Claude Code

    Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.

  5. Watch it handle a test run

    A staged conversation against a simulated world — then it’s live.

A considered pairing

Why Claude Code for this agent

Suppression read before anything

The first call on every event is the suppression state. Where it comes back set, the rules say what to record and the run finishes there.

Consent is not the agent's call

There is no unsuppress operation, no delete and no send. The worst outcome available to it is a property you can change back.

Good to know

Before you fork

Can an event ever result in somebody receiving mail again?

No. Nothing in the workflow sends, triggers or schedules an email, and lifting a suppression is not a wired operation. The agent writes contact properties and posts to Slack. If a suppressed address genuinely needs mail again, that stays a decision a person makes in Loops against whatever consent record justifies it.

Other editions

Run it with a different agent

OpenAICodexopencodeopenclawhermesMore Claude Code agents

Make it yours

Put Loops Subscriber Agent to work on Claude Code.

Free to start. Guided setup, a staged test run, and a workflow you can change at every step.