The problem to solve
Direct mailbox integrations repeat authentication, connection and error-handling work in every project.
Integration guide
n8n email API
Use HTTP Request nodes to send from or read an existing mailbox while keeping its provider credentials outside every n8n workflow.
n8n email APIapikey + apikeyboxn8n HTTP Request → MailBridgeAPI
A practical implementation path
MailBridgeAPI keeps the authorized mailbox connection in one dashboard and gives backend applications account and mailbox API keys for documented HTTP endpoints.
01 — 03
From mailbox to working request
Connect the mailbox
Authorize the mailbox or configure its compatible SMTP and IMAP connection in the MailBridgeAPI dashboard.
Keep keys in the backend
Store the account API key and mailbox API key in server-side environment variables or a secret manager.
Call and verify the endpoint
Run the request, inspect the JSON response and keep the request or message identifier for support.
n8n HTTP Request → MailBridgeAPI
Copy-ready example
Use HTTP Request nodes to send from or read an existing mailbox while keeping its provider credentials outside every n8n workflow.
- One mailbox connection managed centrally
- API access without copying the mailbox password into every project
- Dashboard activity, errors and mailbox health
- A testable path from code to the real mailbox
const body = new URLSearchParams({
apikey: $env.MAILBRIDGE_ACCOUNT_KEY,
apikeybox: $env.MAILBRIDGE_MAILBOX_KEY,
recipient_email: $json.email,
mail_subject: $json.subject,
mail_body: $json.html,
format: 'html',
from_source: 'n8n'
});
return [{ json: await fetch('https://api.mailbridgeapi.com/sendemail/', {method:'POST', body}).then(r=>r.json()) }];Provider and implementation limits
Keep API keys on the server. Do not place them in browser code, public workflow exports or repositories.
LIVE SMTP · IMAP · OAUTH DEMO
Test the real connection before you build
The live demo can validate SMTP, IMAP or a supported OAuth provider and issue temporary API keys without creating an account.