Bot accounts

Email addresses for programs, with a real mailbox and their own token, used with the email API.

  • Category: Communication
  • Status: Available
  • Requirements: A verified professional email domain; A bot-type email plan
  • MCP tools (Read only): listar_cuentas_bot_correo
  • MCP tools (Write or modify): crear_cuenta_bot_correo
  • MCP tools (Destructive): cambiar_token_cuenta_bot_correo, eliminar_cuenta_bot_correo

Markdown

What can you do with it?

A bot account is an address for a program to send and receive email. It has a real mailbox on the server, but nobody logs in with a password: ArduMaker generates its password at random, stores it encrypted and never exposes it.

  • Act as sender for the email API.
  • Receive replies and read them via API or MCP.
  • Authenticate with its own bot_ token in the Email-Bot-Token header.

When should you use it?

When email is handled by an application and not a person: system notices, a bot that replies, a no-reply@ address.

How does it work in ArduMaker?

  1. Choose domain, name, local part and a bot-type plan. Optionally 6, 12 or 18 months prepaid.
  2. ArduMaker creates the mailbox on the server first; if that fails, no half-created bot is left behind.
  3. The bot is saved with its token hash and linked to a service billed monthly.
  4. The response carries the token only once.

For new programs it is better to use an email API key, which can cover several bots; the per-bot token keeps working.

What actually changes?

  • Creation: mailbox on the server, bot in ArduMaker and a billable service.
  • Regenerating the token: the previous one stops working and its open session is cut.
  • Only the display name can change. Address and plan do not: create another bot for that.
  • Removal: the bot and its service are removed; the mailbox is marked deleted but the email inside is not erased.

Expected result

An address ready to send and receive from code. If a bot is created again with the same address, it reuses its mailbox.

Errors and troubleshooting

  • 409 `bot_ya_existe`: there is already an active bot with that address on the domain.
  • 404 `plan_not_found`: the plan does not exist or does not allow bot accounts.
  • 400 `solo_el_nombre`: an attempt was made to change the address or plan.
  • Lost token: it cannot be recovered; regenerate it.

MCP access

Requires access to the domain's company. See /mcp/correo. With the account_id returned on creation, the bot mailbox is read with the webmail tools.

TypeTools
Readlistar_cuentas_bot_correo
Modifycrear_cuenta_bot_correo, cambiar_token_cuenta_bot_correo
Destructiveeliminar_cuenta_bot_correo

Related features