Seven.io
for LuumenAI
Send SMS alerts, check delivery, and keep on-call contacts current
Seven.io handles the SMS and voice side of your operations. Connect it with an API key and Luumen can read your balance, SMS pricing, contact groups, and the message journal for context. When you need to reach people, it drafts the message, shows you who it goes to, and sends after you approve.
The Seven.io toolbox
11 tools: 7 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadFormat Phone NumbersValidate and normalize one or more phone numbers without performing a paid carrier lookup.
- ReadGet AnalyticsReturn Seven.io usage statistics for a date range, optionally grouped by date, label, subaccount, or country.
- ReadGet BalanceReturn the connected Seven.io account's available credit balance and currency.
- ReadGet SMS PricingReturn Seven.io SMS prices, preferably narrowed to one destination country.
- ReadList ContactsList or search Seven.io contacts, optionally restricted to a contact group.
- ReadList Contact GroupsList Seven.io contact groups and their member counts for use in contact filtering or assignment.
- ReadQuery Message JournalQuery one page of outbound SMS, inbound SMS, or voice journal entries using a consistent filter interface.
- WriteCreate ContactCreate a Seven.io contact with identity, address, phone, notes, and group fields. Approval by default
- WriteDelete ContactPermanently delete one Seven.io contact by ID. Approval by default
- WriteSend SMSSend an SMS through Seven.io. Approval by default
- WriteUpdate ContactUpdate selected standard fields or group memberships on an existing Seven.io contact. Approval by default
One prompt, start to finish
What a governed Seven.io 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, delete contact, send sms, update contact — is shown as a plan and requires approval by default, including the 2 actions 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 Seven.io — 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 Seven.io to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.