BlueFox Email
for LuumenAI
Read contacts and lists in BlueFox Email, then send or update with approval
Connect BlueFox Email and your agent can look up a contact, read a subscriber list, and check what state someone is in before anything goes out. Changes — creating a contact, updating a subscriber, sending a transactional or triggered email — are previewed first and go out as approved, audited steps. Luumen authenticates with an API key.
The BlueFox Email toolbox
11 tools: 4 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet ContactRetrieve one contact by its current email address from the specified BlueFox project.
- ReadGet SubscriberRetrieve one subscriber by current email address from a known BlueFox subscriber list.
- ReadList ContactsReturn all contacts in the specified BlueFox project.
- ReadList SubscribersReturn subscribers in one known BlueFox subscriber list.
- WriteCreate ContactCreate a contact in the specified BlueFox project. Approval by default
- WriteDelete ContactPermanently delete a contact by its current email address from the specified BlueFox project. Approval by default
- WriteSend Transactional EmailImmediately send one transactional-template email to an external recipient. Approval by default
- WriteSend Triggered EmailStart a triggered email flow for one or more external recipients. Approval by default
- WriteSubscribe To ListCreate a subscriber-list membership. Approval by default
- WriteUpdate ContactUpdate a contact identified by its current email address in the specified BlueFox project. Approval by default
- WriteUpdate SubscriberUpdate a subscriber's identity, custom data, or state in a known BlueFox list. Approval by default
One prompt, start to finish
What a governed BlueFox Email 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 transactional email, send triggered email, and more — is shown as a plan and requires approval by default, including the 4 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 BlueFox Email — 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 BlueFox Email to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.