Loops.so
for LuumenAI
Read your Loops audience and lists, then change contacts as approved steps.
Connect Loops with an API key and Luumen can look up contacts, read your contact properties, list mailing lists, and see which transactional emails are published. When something needs to change — a contact added, a property updated, an event sent to trigger a send — Luumen shows the exact call first and waits for your approval.
The Loops.so toolbox
11 tools: 6 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadFind ContactSearch for a contact by email or userId.
- ReadGet Contact PropertiesRetrieve a list of your account's contact properties from Loops.so.
- ReadGet Dedicated Sending IPsRetrieve a list of Loops' dedicated sending IP addresses.
- ReadGet Mailing ListsRetrieve all mailing lists associated with your Loops account.
- ReadList Transactional EmailsRetrieve a list of published transactional emails.
- ReadTest API KeyTest API key validity and retrieve team information.
- WriteCreate ContactAdd a new contact to your Loops audience. Approval by default
- WriteCreate Contact PropertyAdd a custom contact property to your Loops team. Approval by default
- WriteDelete ContactDelete a contact by email address or user ID. Approval by default
- WriteSend EventSend events to trigger emails in Loops. Approval by default
- WriteUpdate ContactUpdate an existing contact by email or userId. Approval by default
One prompt, start to finish
What a governed Loops.so run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create contact, create contact property, delete contact, send event, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Loops.so — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut Loops.so to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.