how to add a dedicated email inbox to your flowise chatflow

Most Flowise chatflows hit the same wall eventually.

The chatflow works. It handles the conversation, runs the retrieval, does whatever it was built to do. Then something needs a confirmation email. Or the agent has to sign up for an external service and catch the verification code that comes back. Or you want the chatflow to coordinate with a downstream process over email.

And suddenly you're looking at the Gmail node in Flowise, trying to remember your OAuth credentials, realizing the inbox will be your personal Gmail, and wondering if there's a cleaner path.

There is.

Why Gmail breaks down for chatflow agents#

The Flowise Gmail integration makes sense for a specific use case: a personal assistant that reads and writes your inbox. If that's what you're building, it's fine.

For production chatflows, it creates three real problems. First, you're mixing agent traffic with human email. Every verification code the flow catches, every confirmation it sends, lands in the same inbox you use for actual work. Second, OAuth tokens expire. Your agent hits a wall mid-conversation at 2am and there's nobody around to re-authenticate. Third, one shared inbox means no isolation. If you're running a support chatflow, a research agent, and an onboarding flow, they all fight over the same address.

What the agent actually needs is its own inbox — one it provisions without a human in the loop.

What LobsterMail gives a Flowise chatflow#

LobsterMail is email infrastructure built for agents. Your chatflow can provision a dedicated @lobstermail.ai inbox with no human signup, no OAuth, and no shared credentials. The SDK handles account creation automatically on first use.

npm install @lobsterkit/lobstermail

One call to provision an inbox:

import { LobsterMail } from '@lobsterkit/lobstermail';

const lm = await LobsterMail.create();
const inbox = await lm.createSmartInbox({ name: 'support-flow' });

console.log(inbox.address); // support-flow@lobstermail.ai

LobsterMail.create() registers a free account on first run and stores the token at ~/.lobstermail/token. Every subsequent call reuses it. Your chatflow has a persistent, isolated inbox it owns.

Run multiple chatflows? Give each one a different name. They each get their own address, and there's no cross-contamination.

Wiring it into Flowise#

Flowise doesn't have a native LobsterMail node. You'll use the Custom Tool node with JavaScript. Here's how to set up two patterns that cover most email use cases in chatflows.

Pattern 1: send a confirmation after the conversation#

Drop a Custom Tool node near the end of your chatflow. Name it something your LLM node will understand — send_confirmation_email works well. Define two input fields in the tool schema: recipientEmail (string) and confirmationMessage (string). Then add this code:

const { LobsterMail } = await import('@lobsterkit/lobstermail');

const lm = await LobsterMail.create();
const inbox = await lm.createSmartInbox({ name: 'support-flow' });

await inbox.send({
  to: recipientEmail,
  subject: 'Your request is confirmed',
  text: confirmationMessage,
});

return { sent: true, from: inbox.address };

The LLM node routes to this tool when it determines a confirmation should go out. The recipientEmail and confirmationMessage values come from earlier nodes in the flow — extract them from conversation context or from a form submission node upstream.

Pattern 2: catch verification codes from third-party signups#

This one comes up constantly. Your chatflow signs up for an external service on behalf of a user. The service sends a verification email. The agent needs to read it before continuing.

const { LobsterMail } = await import('@lobsterkit/lobstermail');

const lm = await LobsterMail.create();
const inbox = await lm.createSmartInbox({ name: 'signup-agent' });

// Poll for the latest email
const emails = await inbox.receive({ limit: 5 });
if (emails.length === 0) return { code: null, found: false };

const latest = emails[0];

// Extract a numeric code — pass full body to LLM for flexible parsing
const match = latest.body.match(/\b\d{4,8}\b/);

return {
  code: match ? match[0] : null,
  subject: latest.subject,
  body: latest.body,
  riskScore: latest.riskScore,
};

Feed the result into the next node in your flow. The regex handles predictable formats. If the code format varies, pass body directly to an LLM node and let it extract the value.

A note on the risk score#

LobsterMail returns a riskScore with every received email. That's there to flag prompt injection attempts — cases where a bad actor sends a malicious instruction disguised as a verification code or legitimate reply. For most Flowise chatflows this isn't the primary concern, but if your flow acts autonomously on inbound content, it's worth checking. More on how that works in the security and injection guide.

Managing inboxes as your chatflows scale#

The free tier gives you 1,000 emails per month with no credit card. That covers development and light production workloads comfortably. If you're running chatflows with real volume — hundreds of users per day — the Builder plan at $9/month gets you up to 10 isolated inboxes and 5,000 emails per month.

One inbox per chatflow is a reasonable default. Your support flow gets its own address. Your research agent gets its own. When you need to debug why a confirmation didn't go out, you know exactly which inbox to check and there's no signal buried under other flows' traffic.

What becomes possible#

Once your chatflow has a real inbox, a few things open up that weren't possible before. The flow can handle the full signup-and-verify loop for external services without any human involvement. It can send confirmations from a recognizable, consistent address rather than whatever shared account happened to be available. It can coordinate with other agents and flows over email — which matters more as you start chaining chatflows together. The agent self-signup explained post covers that coordination pattern in depth.

The Gmail node is fine for what it was designed for. For chatflows that need isolated, persistent, agent-owned inboxes, the setup above takes about ten minutes and doesn't require touching your personal credentials again.

Give your chatflow its own email. Get started with LobsterMail — it's free.