Fire the Loops event your sequence is waiting on

Start the sequence that was never instrumented

A companion sends an event for a contact, a name plus any properties the emails reference, and Loops does the rest through whatever automation is listening. Run on a schedule, that is the operations half of lifecycle email, and it covers the long tail nobody will ever ship code for: the trial extended by hand, the customer who finally connected their data source, the enterprise lead who asked for a security review.

How does the contact surface behave?

Lookups are one at a time, by email address or by your own user id.

An audience comes from somewhere a companion can already read: the admin panel, the warehouse export, the spreadsheet the team keeps. Knowing that shapes the plan before you write the prompt.

The write side is a genuine upsert. Updating a contact that does not exist creates it, and custom properties merge into the payload rather than replacing it, so a companion enriching one field will not blank the others. Deleting a contact is available and permanent.

Campaigns, loops and templates are authored in Loops. A transactional send needs a transactional id that already exists there, and the companion supplies the variables the template asks for.

• "Look up this email in Loops and tell me which mailing lists they are on."
• "Fire the trial-extended event with the new end date from the admin panel."

Which sends pause, and which do not?

Worth setting deliberately.

Strawberry keeps a list of actions that always interrupt with an approval card, such as sending Gmail, posting to Slack and texting through Twilio, and the Loops transactional send is not currently on it. A companion asked to send one will ask you in conversation, because that is how the tool is described to it.

For a guaranteed stop, Settings → AI permissions has an Ask Always mode that makes every action prompt regardless of the defaults. Turn it on before the first run and you get the same stop-and-confirm behaviour that email and chat tools have by default.

The other half of the guardrail is structural. Transactional email goes to one address at a time, through a template someone wrote and reviewed, and audience-wide sending stays inside Loops where the unsubscribe machinery lives.

Hand over the messy edge

The trigger with no instrumentation. The contact record that is wrong because the truth lives in three other tabs. The one-off send that would otherwise be a copy-paste at half past six. That is where an hour a week goes. A companion takes all three, the same as any other marketing job.

Loops keeps running the loops and campaigns on its own infrastructure, on schedule, with deliverability, unsubscribes and suppression handled there. A companion feeds that machinery.

Frequently asked questions