AI agent email
for n8n workflows.

1. Provision an identity and add it as an n8n credential

Create a Loomal identity at console.loomal.ai. In n8n, go to Credentials → New → Header Auth (or HTTP Custom Auth), name it 'Loomal API', and set the Authorization header to Bearer loid-your-api-key.

If you have multiple workflows, mint multiple identities — one per workflow — so revocation is surgical.

{
  "name": "Loomal API",
  "type": "httpHeaderAuth",
  "data": {
    "name": "Authorization",
    "value": "Bearer loid-your-api-key"
  }
}

2. Wire Loomal into the AI Agent node via MCP

In the AI Agent node's tool config, add an MCP Client tool. Point it at the Loomal MCP server using the stdio command. The agent now sees mail.send, mail.list_messages, vault.get, and so on as callable tools — no manual schema work.

{
  "server": {
    "command": "npx",
    "args": ["-y", "@loomal/mcp"],
    "env": {
      "LOOMAL_API_KEY": "={{$credentials.loomalApi.value}}"
    }
  },
  "toolFilter": ["mail.send", "mail.list_messages", "mail.reply", "vault.get", "vault.totp"]
}

3. Send mail without the AI Agent node

For non-agent workflows — schedule trigger, database trigger, form trigger — use the HTTP Request node directly. Method POST, URL https://api.loomal.ai/v0/messages/send, Authentication: your Loomal credential, Body: a JSON object with to, subject, and text.

{
  "method": "POST",
  "url": "https://api.loomal.ai/v0/messages/send",
  "authentication": "genericCredentialType",
  "genericAuthType": "httpHeaderAuth",
  "sendBody": true,
  "contentType": "json",
  "jsonBody": "={\n  \"to\": [\"{{$json.email}}\"],\n  \"subject\": \"{{$json.subject}}\",\n  \"text\": \"{{$json.body}}\"\n}"
}

4. Receive mail via webhook

Configure an inbound webhook in the Loomal console pointing to your n8n Webhook node URL. When mail arrives at the agent's address, n8n receives a POST with the message payload and you can branch on labels, sender, or subject from there.

Pair this with the AI Agent node downstream to triage and respond — the webhook delivers the message, the agent decides what to do, mail.reply sends the response in-thread.

{
  "event": "message.received",
  "messageId": "<abc123@loomal.ai>",
  "threadId": "thd_xyz",
  "from": "alice@example.com",
  "subject": "Re: Demo follow-up",
  "extractedText": "Sounds great, can we do Tuesday at 2pm?",
  "labels": ["unread"]
}

5. Use vault for downstream API credentials

When a workflow needs a credential the AI Agent should fetch on demand (Stripe key, CRM token), store it in the Loomal vault and reference it via vault.get. The model never sees the credential value — only the result of using it.

For TOTP-protected logins, the same pattern works with vault.totp. Pre-load the otpauth secret once via the REST API; have the agent call vault.totp by label whenever a code is required.

{
  "method": "POST",
  "url": "https://api.loomal.ai/v0/vault",
  "jsonBody": {
    "label": "stripe-key",
    "value": "sk_live_..."
  }
}