Check sending domains and message activity, then add webhooks with approval
Connect MailerSend and Luumen can answer questions about your transactional email without you opening the dashboard. Which domains are verified, what went out in the last hour, how much of the API quota is left, which sender identities exist. When something needs to change — a new sending domain, an SMTP user, an API token, a webhook — Luumen shows the plan first and waits for your approval.
23 tools: 18 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed MailerSend run looks like inside Luumen.
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 sending domain, create smtp user, create api token, create webhook, 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 MailerSend — 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.
Connect in minutes. Every action scoped, approved, and audited from day one.