Read audiences, contacts, and broadcasts. Send changes through approval.
Resend handles the mail your systems send: incident notices, maintenance windows, status updates. Connect it with an API key and Luumen can read audiences, contacts, templates, broadcasts, and webhooks on request. Changes — a new contact, a draft broadcast, a deleted API key — are previewed first and go out only after you approve them.
66 tools: 28 read, 38 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Resend 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.
This connection exposes write actions such as add contact to segment, cancel email, create api key, create audience, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Resend — 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.