Review lifecycle email in Loops
Connect Loops read-only and prepare a weekly review of campaign, loop, and transactional email performance.
The Loops lifecycle email review template reads the campaigns, loops, and
transactional emails sent in the review window with their delivery, open,
click, and unsubscribe metrics, then reports which sends moved materially
against the previous window, which lifecycle loops have steps with weak
engagement, and which audiences are shrinking, citing the campaign or loop
behind each finding. It follows the emails marketing skill: measure the
lifecycle system, keep audience privacy explicit, propose the next experiment,
and leave sends to a person.
Enable and connect Loops
Loops MCP became generally available on September 1, 2026. Its authorization
server at app.loops.so accepts Client ID Metadata Documents or preregistered
clients rather than open dynamic registration, so an operator must configure
LOOPS_MCP_OAUTH_CLIENT_ID and LOOPS_MCP_OAUTH_CLIENT_SECRET before
enabling MANAGED_MCP_LOOPS_ENABLED. Then connect the Loops card and
authorize with your own Loops login. Work on Repeat requests the single mcp
scope.
Set the variable
| Key | Example | Why it is a variable |
|---|---|---|
reviewWindowDays | 7 | The window should match the schedule; widen it for a monthly run without rewriting the instructions. |
Reference it in the instructions as {{reviewWindowDays}}.
Current beta boundary
Loops is connection-only until exact authenticated tool schemas are captured and reviewed, so the packaged routine ships as a preview. After review, the first manifest should stay with campaign, loop, transactional, and contact reads; creating, editing, scheduling, sending, and deleting emails, loops, or contacts must be classified separately and approval-gated.
Recovery
If authorization expires or is revoked, the connection moves to
reauthorization_required; reconnect the same card to update it in place.