Mailgent for n8n
Use Mailgent inside n8n workflows over plain HTTP. Trigger on inbound email, send replies, store secrets, and pay — giving your automations a real agent identity.
n8n automations talk to anything with an HTTP API, and Mailgent is just that. Use the HTTP Request node to send mail, read the inbox, fetch a secret, or trigger a payment as steps in a workflow.
That gives a no-code/low-code workflow the same agent identity a coded agent gets: a real address, a vault, and the rest, all gated by a scoped key.
Call the API from a node
Add an HTTP Request node pointed at the Mailgent API with the agent's bearer token. Send an email when a workflow fires, or poll the inbox to branch on incoming mail.
Store the key in n8n credentials so it isn't hardcoded in the workflow.
POST https://api.mailgent.dev/v0/mail/send
Authorization: Bearer mgnt-...
Content-Type: application/json
{ "to": "{{$json.email}}", "subject": "Update", "text": "{{$json.body}}" }Inbound as a trigger
Poll the agent's inbox on a schedule and branch on new messages, so a workflow can react to email a customer or system sends — turning Mailgent into both an action and a trigger in your automations.
FAQ
Do I need a custom node?
No. The built-in HTTP Request node is enough to call any Mailgent endpoint.
Can a workflow react to incoming email?
Yes. Poll the inbox on a schedule and branch on unread messages.
Give your agent an inbox.
A real email address, a vault, 2FA, and an identity in one API call.