> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Mandrill (Mailchimp Transactional)

The Mandrill (Mailchimp Transactional) connector lets your AI agent act in each user's Mandrill (Mailchimp Transactional) account. Each user connects their own Mandrill (Mailchimp Transactional) API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 61 tools.

**Authentication:** API Key
**Categories:** Communication, Marketing
**Tools:** 61: 33 read, 18 write, 10 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=MANDRILL)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Mandrill (Mailchimp Transactional) connection

   In **AgentKit > Connections**, create a Mandrill (Mailchimp Transactional) connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'mandrill'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Mandrill (Mailchimp Transactional):', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'mandrill_user_info_get',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "mandrill"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Mandrill (Mailchimp Transactional):", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="mandrill_user_info_get",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Mandrill (Mailchimp Transactional) credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'mandrill_allowlist_list',
  toolInput: {},
  connector: 'mandrill',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="mandrill_allowlist_list",
    tool_input={},
    connection_name="mandrill",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `mandrill_allowlist_list`

List Allowlist · Read-only

List addresses on the allowlist, which are never added to the denylist automatically.
Returns an array with email, detail and created_at.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, optional): An optional email address or prefix to search by. Example: jane@example.com

Example input: `{}`

### `mandrill_inbound_domain_check`

Check Inbound Domain · Read-only

Check an inbound domain's MX records now.
Returns domain, created_at and valid_mx.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): An existing inbound domain. Example: mail.example.com

Example input: `{"domain":"<domain>"}`

### `mandrill_inbound_domains_list`

List Inbound Domains · Read-only

List the domains configured to receive inbound email.
Returns an array with domain, created_at and valid_mx.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mandrill_inbound_routes_list`

List Inbound Routes · Read-only

List the mailbox routes for an inbound domain.
Returns an array with id, pattern and url.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, optional): The domain to check (required if phone is not provided) Example: mail.example.com
- `phone` (`string`, optional): The SMS program phone number (required if domain is not provided) Example: +15551234567

Example input: `{}`

### `mandrill_message_content_get`

Get Message Content · Read-only

Retrieve the full content (subject, from, to, headers, HTML, text and attachments) of a recently sent message.
Returns ts, _id, from_email, from_name, subject, to, tags, headers, text, html and attachments. Content is kept only for a few days.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): Message ID (_id) of a recently sent message. Example: abc123abc123abc123abc123abc123

Example input: `{"id":"<id>"}`

### `mandrill_message_info_get`

Get Message Info · Read-only

Retrieve the delivery details of one sent message.
Returns ts, _id, sender, template, subject, email, tags, opens, opens_detail, clicks, clicks_detail, state, metadata and smtp_events.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): Message ID (_id) returned when the message was sent or by mandrill_messages_search. Example: abc123abc123abc123abc123abc123

Example input: `{"id":"<id>"}`

### `mandrill_message_parse`

Parse MIME Message · Read-only

Parse a raw MIME message into its parts without sending it.
Returns subject, from_email, from_name, to, headers, text, html, attachments and images.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `raw_message` (`string`, required): The full MIME document of an email message. Example: From: orders@example.com
To: jane@example.com
Subject: Hi

Hello

Example input: `{"raw_message":"<raw_message>"}`

### `mandrill_messages_search`

Search Messages · Read-only

Search recently sent messages (up to 90 days, depending on retention) by query, date range, tags, senders or API keys.
Returns an array of messages with ts, _id, sender, template, subject, email, tags, opens, clicks, state, metadata and smtp_events.
Use this to find messages. Use mandrill_message_info_get for one message's details.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `api_keys` (`array`, optional): An array of API keys to narrow the search to, will return messages sent by ANY of the keys. Example: ["Aq1Bc2De3Fg4Hi5Jk6Lm7"]
- `date_from` (`string`, optional): Start date. Example: 2026-11-01
- `date_to` (`string`, optional): End date. Example: 2026-11-13
- `limit` (`integer`, optional): The maximum number of results to return, defaults to 100, 1000 is the maximum. Example: 100
- `query` (`string`, optional): Search terms to find matching messages. Example: email:jane@example.com AND tags:receipts
- `senders` (`array`, optional): An array of sender addresses to narrow the search to, will return messages sent by ANY of the senders. Example: ["orders@example.com"]
- `tags` (`array`, optional): An array of tag names to narrow the search to, will return messages that contain ANY of the tags. Example: ["password-reset"]

Example input: `{}`

### `mandrill_messages_search_time_series`

Search Message Statistics by Hour · Read-only

Count sent messages matching a search, bucketed by hour.
Returns an array of hourly stats with time, sent, hard_bounces, soft_bounces, rejects, complaints, unsubs, opens, unique_opens, clicks and unique_clicks.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `date_from` (`string`, optional): Start date. Example: 2026-11-01
- `date_to` (`string`, optional): End date. Example: 2026-11-13
- `query` (`string`, optional): The search terms to find matching messages for. Example: email:jane@example.com AND tags:receipts
- `senders` (`array`, optional): An array of sender addresses to narrow the search to, will return messages sent by ANY of the senders. Example: ["orders@example.com"]
- `tags` (`array`, optional): An array of tag names to narrow the search to, will return messages that contain ANY of the tags. Example: ["password-reset"]

Example input: `{}`

### `mandrill_metadata_fields_list`

List Metadata Fields · Read-only

List the custom metadata fields indexed for the account (used to search messages by metadata).
Returns an array with name, state and view_template.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mandrill_rejects_list`

List Denylist · Read-only

List addresses on the denylist (rejects), which Mandrill will not send to, optionally for one address or subaccount.
Returns an array with email, reason (hard-bounce, soft-bounce, spam, unsub, custom), detail, created_at, expires_at, expired and sender.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, optional): An optional email address to search by. Example: jane@example.com
- `include_expired` (`boolean`, optional): Whether to include rejections that have already expired. Example: false
- `subaccount` (`string`, optional): An optional unique identifier for the subaccount to limit the denylist. Example: cust-123

Example input: `{}`

### `mandrill_scheduled_messages_list`

List Scheduled Messages · Read-only

List messages scheduled to be sent later, optionally only those to one recipient.
Returns an array with _id, created_at, send_at, from_email, to and subject.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `to` (`string`, optional): Only scheduled messages to this recipient address. Example: jane@example.com

Example input: `{}`

### `mandrill_sender_domain_check`

Check Sender Domain · Read-only

Check a sending domain's SPF and DKIM DNS records now.
Returns domain, spf and dkim (each with valid, valid_after and error), verified_at and valid_signing.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): A domain name. Example: mail.example.com

Example input: `{"domain":"<domain>"}`

### `mandrill_sender_domains_list`

List Sender Domains · Read-only

List sending domains with their SPF, DKIM and verification status.
Returns an array with domain, created_at, last_tested_at, spf, dkim, verified_at and valid_signing.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mandrill_sender_info_get`

Get Sender Statistics · Read-only

Get detailed statistics for one sender address (today, last 7, 30, 60 and 90 days).
Returns address, created_at, sent, hard_bounces, soft_bounces, rejects, complaints, unsubs, opens, clicks and stats.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `address` (`string`, required): The email address of the sender. Example: orders@example.com

Example input: `{"address":"<address>"}`

### `mandrill_sender_time_series_get`

Get Sender Statistics by Hour · Read-only

Get hourly statistics for one sender address over the last 30 days.
Returns an array with time, sent, hard_bounces, soft_bounces, rejects, complaints, opens and clicks.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `address` (`string`, required): The email address of the sender. Example: orders@example.com

Example input: `{"address":"<address>"}`

### `mandrill_senders_list`

List Senders · Read-only

List the sender addresses that have sent through the account, with their statistics.
Returns an array with address, created_at, sent, hard_bounces, soft_bounces, rejects, complaints, unsubs, opens, clicks, unique_opens and unique_clicks.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mandrill_subaccount_info_get`

Get Subaccount · Read-only

Retrieve one subaccount with its statistics.
Returns id, name, notes, custom_quota, status, reputation, sent_total, sent_hourly, hourly_quota and last_30_days.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique identifier of the subaccount to query. Example: 1

Example input: `{"id":"<id>"}`

### `mandrill_subaccounts_list`

List Subaccounts · Read-only

List the account's subaccounts, optionally filtered by ID prefix.
Returns an array with id, name, custom_quota, status, reputation, created_at, sent_total, sent_hourly and hourly_quota.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `q` (`string`, optional): An optional prefix to filter the subaccounts' ids and names. Example: cust

Example input: `{}`

### `mandrill_tag_info_get`

Get Tag Statistics · Read-only

Get detailed statistics for one tag (today, last 7, 30, 60 and 90 days).
Returns tag, sent, hard_bounces, soft_bounces, rejects, complaints, unsubs, opens, clicks and stats.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `tag` (`string`, required): An existing tag name. Example: password-reset

Example input: `{"tag":"<tag>"}`

### `mandrill_tag_time_series_get`

Get Tag Statistics by Hour · Read-only

Get hourly statistics for one tag over the last 30 days.
Returns an array with time, sent, hard_bounces, soft_bounces, rejects, complaints, opens and clicks.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `tag` (`string`, required): An existing tag name. Example: password-reset

Example input: `{"tag":"<tag>"}`

### `mandrill_tags_all_time_series_get`

Get All Tags Statistics by Hour · Read-only

Get hourly statistics across all tags over the last 30 days.
Returns an array with time, sent, hard_bounces, soft_bounces, rejects, complaints, opens and clicks.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mandrill_tags_list`

List Tags · Read-only

List the tags used on sent messages, with their totals.
Returns an array with tag, reputation, sent, hard_bounces, soft_bounces, rejects, complaints, unsubs, opens, clicks, unique_opens and unique_clicks.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mandrill_template_info_get`

Get Template · Read-only

Retrieve one template, including its draft and published code.
Returns slug, name, labels, code, subject, from_email, from_name, text, publish_code, publish_subject and published_at.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, required): The immutable name of an existing template. Example: order-shipped

Example input: `{"name":"<name>"}`

### `mandrill_template_render`

Render Template · Read-only

Render a template's HTML with editable content and merge variables, without sending.
Returns html, the rendered result.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `template_content` (`array`, required): Content for the template's editable regions, each with name and content. Send an empty array when there are none. Example: [{"name": "header", "content": "<h1>Hi</h1>"}]
- `template_name` (`string`, required): Name (slug) of the Mandrill template. Example: order-shipped
- `merge_vars` (`array`, optional): Optional merge variables to use for injecting merge field content. If this is not provided, no merge fields will be replaced. Example: [{"name": "FNAME", "content": "Jane"}]

Example input: `{"template_content":[{"name":"header","content":"<h1>Hi</h1>"}],"template_name":"<template_name>"}`

### `mandrill_template_time_series_get`

Get Template Statistics · Read-only

Get hourly sending statistics for one template over the last 30 days.
Returns an array with time, sent, hard_bounces, soft_bounces, rejects, complaints, unsubs, opens, unique_opens, clicks and unique_clicks.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, required): The name of an existing template. Example: order-shipped

Example input: `{"name":"<name>"}`

### `mandrill_templates_list`

List Templates · Read-only

List the Mandrill templates in the account, optionally by label.
Returns an array of templates with slug, name, labels, subject, from_email, from_name, code, publish_code, published_at, created_at and updated_at.
Use mandrill_template_info_get for one template.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `label` (`string`, optional): An optional label to filter the templates. Example: receipts

Example input: `{}`

### `mandrill_tracking_domain_check`

Check Tracking Domain · Read-only

Check a tracking domain's CNAME record now.
Returns domain, cname (valid, valid_after, error) and valid_tracking.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): An existing tracking domain name. Example: mail.example.com

Example input: `{"domain":"<domain>"}`

### `mandrill_tracking_domains_list`

List Tracking Domains · Read-only

List custom click and open tracking domains with their CNAME status.
Returns an array with domain, created_at, last_tested_at, cname (valid, valid_after, error) and valid_tracking.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mandrill_user_info_get`

Get Account Info · Read-only

Retrieve the account's username, reputation, hourly quota, backlog and sending statistics.
Returns username, created_at, public_id, reputation, hourly_quota, backlog and stats (today, last 7, 30, 60, 90 days, all time).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mandrill_user_ping`

Ping · Read-only

Check that the API key works.
Returns PING with the value PONG!.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mandrill_webhook_info_get`

Get Webhook · Read-only

Retrieve one webhook.
Returns id, url, description, auth_key, events, created_at, last_sent_at, batches_sent, events_sent and last_error.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`integer`, required): The unique identifier of a webhook belonging to this account. Example: 1

Example input: `{"id":1}`

### `mandrill_webhooks_list`

List Webhooks · Read-only

List the webhooks configured for the account.
Returns an array with id, url, description, auth_key, events, created_at, last_sent_at, batches_sent, events_sent and last_error.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mandrill_allowlist_add`

Add to Allowlist · Write

Add an address to the allowlist so bounces never denylist it.
Returns email and whether it was added.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, required): An email address to add to the allowlist. Example: jane@example.com
- `comment` (`string`, optional): An optional description of why the email was added to the allowlist. Example: Requested removal

Example input: `{"email":"<email>"}`

### `mandrill_inbound_domain_add`

Add Inbound Domain · Write

Add a domain to receive inbound email. Point its MX records at Mandrill.
Returns domain, created_at and valid_mx.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): A domain name; Validation: strip_tags, required. Example: mail.example.com

Example input: `{"domain":"<domain>"}`

### `mandrill_inbound_route_add`

Add Inbound Route · Write

Route inbound email whose local part matches a pattern (for example support-*) on an inbound domain to your webhook URL.
Returns the route's id, pattern and url.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `url` (`string`, required): The webhook URL where the inbound messages will be published. Example: https://example.com/mandrill/webhook
- `domain` (`string`, optional): An existing inbound domain (required if phone is not provided) Example: inbound.example.com
- `pattern` (`string`, optional): For email: the mailbox pattern (e.g., "mailbox-*"). For SMS: not used, the phone number is the pattern. Example: support-*
- `phone` (`string`, optional): The SMS program phone number - the TO number that receives inbound SMS (required if domain is not provided) Example: +15551234567

Example input: `{"url":"<url>"}`

### `mandrill_inbound_route_update`

Update Inbound Route · Write

Change an inbound route's pattern or URL.
Returns the updated route.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique identifier of an existing mailbox route. Example: 7.a1b2c3d4e5f6a7b8
- `pattern` (`string`, optional): For email: The search pattern that the mailbox name should match. For SMS: the sender's phone number (FROM number). Null to leave unchanged. Example: support-*
- `url` (`string`, optional): The webhook URL where the inbound messages will be published; Validation: webhookexists. Example: https://example.com/mandrill/webhook

Example input: `{"id":"<id>"}`

### `mandrill_message_send`

Send Email · Write

Send a transactional email with inline HTML or text content to one or more recipients.
Returns an array with one result per recipient: email, status (sent, queued, scheduled, rejected or invalid), reject_reason and _id (the message ID).
Use this for inline content. Use mandrill_message_send_template to send a stored template.
Prerequisite: the from domain should be verified in Mandrill (see mandrill_sender_domains_list).

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `to` (`array`, required): Recipients, each an object with email, an optional name, and an optional type (to, cc or bcc; defaults to to) Example: [{"email": "jane@example.com", "name": "Jane Doe", "type": "to"}]
- `async` (`boolean`, optional): Enable a background sending mode that is optimized for bulk sending. In async mode, messages/send will immediately return a status of "queued" for every recipient. To handle rejections when sending in async mode, set up a webhook for the 'reject' event. Example: false
- `attachments` (`array`, optional): Attachments, each with type (MIME type), name (file name) and content (the file as base64) Example: [{"type": "application/pdf", "name": "invoice.pdf", "content": "JVBERi0xLjQK"}]
- `auto_html` (`boolean`, optional): Whether or not to automatically generate an HTML part for messages that are not given HTML. Example: true
- `auto_text` (`boolean`, optional): Whether or not to automatically generate a text part for messages that are not given text. Example: true
- `bcc_address` (`string`, optional): An optional address to receive an exact copy of each recipient's email. Example: archive@example.com
- `from_email` (`string`, optional): The sender email address. Example: orders@example.com
- `from_name` (`string`, optional): Optional from name to be used. Example: Acme Orders
- `global_merge_vars` (`array`, optional): Global merge variables to use for all recipients. You can override these per recipient. Example: [{"name": "ORDERID", "content": "A1001"}]
- `google_analytics_campaign` (`string`, optional): Optional string indicating the value to set for the utm_campaign tracking parameter. If this isn't provided the email's from address will be used instead. Example: order-emails
- `google_analytics_domains` (`array`, optional): An array of strings indicating for which any matching URLs will automatically have Google Analytics parameters appended to their query string automatically. Example: ["example.com"]
- `headers` (`object`, optional): Optional extra headers to add to the message (most headers are allowed) Example: {"Reply-To": "help@example.com"}
- `html` (`string`, optional): The full HTML content to be sent. Example: Hi *|FNAME|*, your order shipped.

- `images` (`array`, optional): Inline images, each with type (an image/ MIME type), name (the Content-ID used as cid:name in the HTML) and content (base64) Example: [{"type": "image/png", "name": "logo", "content": "iVBORw0KGgo="}]
- `important` (`boolean`, optional): Whether or not this message is important, and should be delivered ahead of non-important messages. Example: true
- `inline_css` (`boolean`, optional): Whether or not to automatically inline all CSS styles provided in the message HTML - only for HTML documents less than 256KB in size. Example: true
- `ip_pool` (`string`, optional): The name of the dedicated ip pool that should be used to send the message. If you do not have any dedicated IPs, this parameter has no effect. If you specify a pool that does not exist, your default pool will be used instead. Example: Main Pool
- `merge` (`boolean`, optional): Whether to evaluate merge tags in the message. Will automatically be set to true if either merge_vars or global_merge_vars are provided. Example: true
- `merge_language` (`string`, optional): The merge tag language to use when evaluating merge tags, either mailchimp or handlebars. Example: mailchimp. One of: `mailchimp`, `handlebars`.
- `merge_vars` (`array`, optional): Per-recipient merge variables that override global_merge_vars. Each item has rcpt (the recipient email) and vars (a list of name and content pairs) Example: [{"rcpt": "jane@example.com", "vars": [{"name": "FNAME", "content": "Jane"}]}]
- `metadata` (`object`, optional): Metadata an associative array of user metadata. Mandrill will store this metadata and make it available for retrieval. In addition, you can select up to 10 metadata fields to index and make searchable using the Mandrill search api. Example: {"order_id": "A1001"}
- `preserve_recipients` (`boolean`, optional): Whether or not to expose all recipients in to "To" header for each email. Example: true
- `recipient_metadata` (`array`, optional): Per-recipient metadata. Each item has rcpt (the recipient email) and values (an object of metadata) Example: [{"rcpt": "jane@example.com", "values": {"user_id": 42}}]
- `return_path_domain` (`string`, optional): A custom domain to use for the messages's return-path. Example: bounce.example.com
- `send_at` (`string`, optional): When to send, as a UTC timestamp in YYYY-MM-DD HH:MM:SS format. Scheduling needs a paid account with prepaid credit; leave empty to send now. Example: 2026-11-20 09:00:00
- `signing_domain` (`string`, optional): A custom domain to use for SPF/DKIM signing instead of mandrill (for "via" or "on behalf of" in email clients) Example: mail.example.com
- `subaccount` (`string`, optional): The unique id of a subaccount for this message - must already exist or will fail with an error. Example: cust-123
- `subject` (`string`, optional): The message subject. Example: Your order has shipped
- `tags` (`array`, optional): An array of string to tag the message with. Stats are accumulated using tags, though we only store the first 100 we see, so this should not be unique or change frequently. Tags should be 50 characters or less. Any tags starting with an underscore are reserved for internal use and will cause errors. Example: ["order-shipped"]
- `text` (`string`, optional): Optional full text content to be sent. Example: Hi *|FNAME|*, your order shipped.
- `track_clicks` (`boolean`, optional): Whether or not to turn on click tracking for the message. Example: true
- `track_opens` (`boolean`, optional): Whether or not to turn on open tracking for the message. Example: true
- `tracking_domain` (`string`, optional): A custom domain to use for tracking opens and clicks instead of mandrillapp.com. Example: click.example.com
- `url_strip_qs` (`boolean`, optional): Whether or not to strip the query string from URLs when aggregating tracked URL data. Example: true
- `view_content_link` (`boolean`, optional): Set to false to remove content logging for sensitive emails. Example: true

Example input: `{"to":[{"email":"jane@example.com","name":"Jane Doe","type":"to"}]}`

### `mandrill_message_send_raw`

Send Raw MIME Email · Write

Send a complete pre-built MIME message, optionally overriding the sender and recipients.
Returns an array with one result per recipient: email, status (sent, queued, scheduled, rejected or invalid), reject_reason and _id (the message ID).

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `raw_message` (`string`, required): The full MIME document of an email message. Example: From: orders@example.com
To: jane@example.com
Subject: Hi

Hello
- `async` (`boolean`, optional): Enable a background sending mode that is optimized for bulk sending. In async mode, messages/sendRaw will immediately return a status of "queued" for every recipient. To handle rejections when sending in async mode, set up a webhook for the 'reject' event. Example: false
- `from_email` (`string`, optional): Optionally define the sender address - otherwise we'll use the address found in the provided headers. Example: orders@example.com
- `from_name` (`string`, optional): Optionally define the sender alias. Example: Acme Orders
- `ip_pool` (`string`, optional): The name of the dedicated ip pool that should be used to send the message. If you do not have any dedicated IPs, this parameter has no effect. If you specify a pool that does not exist, your default pool will be used instead. Example: Main Pool
- `return_path_domain` (`string`, optional): A custom domain to use for the messages's return-path. Example: example.com
- `send_at` (`string`, optional): When to send, as a UTC timestamp in YYYY-MM-DD HH:MM:SS format. Scheduling needs a paid account with prepaid credit; leave empty to send now. Example: 2026-11-20 09:00:00
- `to` (`array`, optional): Recipients to send to instead of the addresses in the MIME headers. Example: ["jane@example.com"]

Example input: `{"raw_message":"<raw_message>"}`

### `mandrill_message_send_template`

Send Email with Template · Write

Send a transactional email using a stored Mandrill template, filling its editable regions and merge tags.
Returns an array with one result per recipient: email, status (sent, queued, scheduled, rejected or invalid), reject_reason and _id (the message ID).
Use this for stored templates (see mandrill_templates_list). Use mandrill_message_send for inline content.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `template_content` (`array`, required): Content for the template's editable regions (mc:edit), each an object with name and content. Send an empty array when the template has none. Example: [{"name": "header", "content": "<h1>Order shipped</h1>"}]
- `template_name` (`string`, required): Name (slug) of the Mandrill template. Example: order-shipped
- `to` (`array`, required): Recipients, each an object with email, an optional name, and an optional type (to, cc or bcc; defaults to to) Example: [{"email": "jane@example.com", "name": "Jane Doe", "type": "to"}]
- `async` (`boolean`, optional): Enable a background sending mode that is optimized for bulk sending. In async mode, messages/send will immediately return a status of "queued" for every recipient. To handle rejections when sending in async mode, set up a webhook for the 'reject' event. Example: false
- `attachments` (`array`, optional): Attachments, each with type (MIME type), name (file name) and content (the file as base64) Example: [{"type": "application/pdf", "name": "invoice.pdf", "content": "JVBERi0xLjQK"}]
- `auto_html` (`boolean`, optional): Whether or not to automatically generate an HTML part for messages that are not given HTML. Example: true
- `auto_text` (`boolean`, optional): Whether or not to automatically generate a text part for messages that are not given text. Example: true
- `bcc_address` (`string`, optional): An optional address to receive an exact copy of each recipient's email. Example: archive@example.com
- `from_email` (`string`, optional): The sender email address. Example: orders@example.com
- `from_name` (`string`, optional): Optional from name to be used. Example: Acme Orders
- `global_merge_vars` (`array`, optional): Global merge variables to use for all recipients. You can override these per recipient. Example: [{"name": "ORDERID", "content": "A1001"}]
- `google_analytics_campaign` (`string`, optional): Optional string indicating the value to set for the utm_campaign tracking parameter. If this isn't provided the email's from address will be used instead. Example: order-emails
- `google_analytics_domains` (`array`, optional): An array of strings indicating for which any matching URLs will automatically have Google Analytics parameters appended to their query string automatically. Example: ["example.com"]
- `headers` (`object`, optional): Optional extra headers to add to the message (most headers are allowed) Example: {"Reply-To": "help@example.com"}
- `html` (`string`, optional): Optional full HTML content to be sent if not in template. Example: Hi *|FNAME|*, your order shipped.

- `images` (`array`, optional): Inline images, each with type (an image/ MIME type), name (the Content-ID used as cid:name in the HTML) and content (base64) Example: [{"type": "image/png", "name": "logo", "content": "iVBORw0KGgo="}]
- `important` (`boolean`, optional): Whether or not this message is important, and should be delivered ahead of non-important messages. Example: true
- `inline_css` (`boolean`, optional): Whether or not to automatically inline all CSS styles provided in the message HTML - only for HTML documents less than 256KB in size. Example: true
- `ip_pool` (`string`, optional): The name of the dedicated ip pool that should be used to send the message. If you do not have any dedicated IPs, this parameter has no effect. If you specify a pool that does not exist, your default pool will be used instead. Example: Main Pool
- `merge` (`boolean`, optional): Whether to evaluate merge tags in the message. Will automatically be set to true if either merge_vars or global_merge_vars are provided. Example: true
- `merge_language` (`string`, optional): The merge tag language to use when evaluating merge tags, either mailchimp or handlebars. Example: mailchimp. One of: `mailchimp`, `handlebars`.
- `merge_vars` (`array`, optional): Per-recipient merge variables that override global_merge_vars. Each item has rcpt (the recipient email) and vars (a list of name and content pairs) Example: [{"rcpt": "jane@example.com", "vars": [{"name": "FNAME", "content": "Jane"}]}]
- `metadata` (`object`, optional): Metadata an associative array of user metadata. Mandrill will store this metadata and make it available for retrieval. In addition, you can select up to 10 metadata fields to index and make searchable using the Mandrill search api. Example: {"order_id": "A1001"}
- `preserve_recipients` (`boolean`, optional): Whether or not to expose all recipients in to "To" header for each email. Example: true
- `recipient_metadata` (`array`, optional): Per-recipient metadata. Each item has rcpt (the recipient email) and values (an object of metadata) Example: [{"rcpt": "jane@example.com", "values": {"user_id": 42}}]
- `return_path_domain` (`string`, optional): A custom domain to use for the messages's return-path. Example: bounce.example.com
- `send_at` (`string`, optional): When to send, as a UTC timestamp in YYYY-MM-DD HH:MM:SS format. Scheduling needs a paid account with prepaid credit; leave empty to send now. Example: 2026-11-20 09:00:00
- `signing_domain` (`string`, optional): A custom domain to use for SPF/DKIM signing instead of mandrill (for "via" or "on behalf of" in email clients) Example: mail.example.com
- `subaccount` (`string`, optional): The unique id of a subaccount for this message - must already exist or will fail with an error. Example: cust-123
- `subject` (`string`, optional): The message subject. Example: Your order has shipped
- `tags` (`array`, optional): An array of string to tag the message with. Stats are accumulated using tags, though we only store the first 100 we see, so this should not be unique or change frequently. Tags should be 50 characters or less. Any tags starting with an underscore are reserved for internal use and will cause errors. Example: ["order-shipped"]
- `text` (`string`, optional): Optional full text content to be sent. Example: Hi *|FNAME|*, your order shipped.
- `track_clicks` (`boolean`, optional): Whether or not to turn on click tracking for the message. Example: true
- `track_opens` (`boolean`, optional): Whether or not to turn on open tracking for the message. Example: true
- `tracking_domain` (`string`, optional): A custom domain to use for tracking opens and clicks instead of mandrillapp.com. Example: click.example.com
- `url_strip_qs` (`boolean`, optional): Whether or not to strip the query string from URLs when aggregating tracked URL data. Example: true
- `view_content_link` (`boolean`, optional): Set to false to remove content logging for sensitive emails. Example: true

Example input: `{"template_content":[{"name":"header","content":"<h1>Order shipped</h1>"}],"template_name":"<template_name>","to":[{"email":"jane@example.com","name":"Jane Doe","type":"to"}]}`

### `mandrill_metadata_field_add`

Add Metadata Field · Write

Add a custom metadata field to index on sent messages.
Returns name, state and view_template.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Metadata field name to index. Example: order_id
- `view_template` (`string`, optional): Mustache template to control how the metadata is rendered in your activity log. Example: {{name}}

Example input: `{"name":"<name>"}`

### `mandrill_reject_add`

Add to Denylist · Write

Add an address to the denylist so Mandrill stops sending to it.
Returns email and added (true when it was not already listed).

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, required): An email address to block. Example: jane@example.com
- `comment` (`string`, optional): An optional comment describing the rejection. Example: Requested removal
- `subaccount` (`string`, optional): An optional unique identifier for the subaccount to limit the denylist entry. Example: cust-123

Example input: `{"email":"<email>"}`

### `mandrill_scheduled_message_reschedule`

Reschedule Message · Write

Change when a scheduled message will be sent.
Returns the message's _id, created_at, send_at, from_email, to and subject.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): Scheduled message ID from mandrill_scheduled_messages_list. Example: abc123abc123abc123abc123abc123
- `send_at` (`string`, required): New send time, UTC, YYYY-MM-DD HH:MM:SS. Example: 2026-11-21 09:00:00

Example input: `{"id":"<id>","send_at":"<send_at>"}`

### `mandrill_sender_domain_add`

Add Sender Domain · Write

Add a sending domain to the account.
Returns domain, spf, dkim, verified_at and valid_signing. Next verify it with mandrill_sender_domain_verify.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): A domain name. Example: mail.example.com

Example input: `{"domain":"<domain>"}`

### `mandrill_sender_domain_verify`

Verify Sender Domain · Write

Send a verification email to a mailbox at a sending domain to prove ownership.
Returns status (sent or already_verified) and domain.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domain` (`string`, required): Domain name at which you can receive email. Example: mail.example.com
- `mailbox` (`string`, required): A mailbox at the domain where the verification email should be sent. Example: postmaster

Example input: `{"domain":"<domain>","mailbox":"<mailbox>"}`

### `mandrill_template_add`

Create Template · Write

Create a template. It stays a draft unless publish is true.
Returns the new template's slug, name, code and publish fields.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Template name; its slug is derived from it and used to send. Example: Order Shipped
- `code` (`string`, optional): The HTML code for the template with mc:edit attributes for the editable elements. Example: Hi *|FNAME|*, your order *|ORDERID|* shipped.

- `from_email` (`string`, optional): A default sending address for emails sent using this template. Example: orders@example.com
- `from_name` (`string`, optional): A default from name to be used. Example: Acme Orders
- `labels` (`array`, optional): An optional array of up to 10 labels to use for filtering templates. Example: ["receipts"]
- `publish` (`boolean`, optional): Set to false to add a draft template without publishing. Example: true
- `subject` (`string`, optional): A default subject line to be used. Example: Your order has shipped
- `text` (`string`, optional): A default text part to be used when sending with this template. Example: Hi *|FNAME|*, your order shipped.

Example input: `{"name":"<name>"}`

### `mandrill_template_publish`

Publish Template · Write

Publish a template's current draft so sends use it.
Returns the template with its new publish fields.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, required): The immutable name of an existing template. Example: order-shipped

Example input: `{"name":"<name>"}`

### `mandrill_template_update`

Update Template · Write

Update a template's draft code, subject, sender, text or labels, and optionally publish it.
Returns the updated template.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, required): The immutable name of an existing template. Example: order-shipped
- `code` (`string`, optional): The new code for the template. Example: Hi *|FNAME|*, your order *|ORDERID|* shipped.

- `from_email` (`string`, optional): The new default sending address. Example: orders@example.com
- `from_name` (`string`, optional): The new default from name. Example: Acme Orders
- `labels` (`array`, optional): An optional array of up to 10 labels to use for filtering templates. Example: ["receipts"]
- `publish` (`boolean`, optional): Set to false to update the draft version of the template without publishing. Example: true
- `subject` (`string`, optional): The new default subject line. Example: Your order has shipped
- `text` (`string`, optional): The new default text part to be used. Example: Hi *|FNAME|*, your order shipped.

Example input: `{"name":"<name>"}`

### `mandrill_tracking_domain_add`

Add Tracking Domain · Write

Add a custom tracking domain. Point its CNAME at Mandrill, then check it with mandrill_tracking_domain_check.
Returns domain, cname and valid_tracking.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): A domain name. Example: mail.example.com

Example input: `{"domain":"<domain>"}`

### `mandrill_webhook_add`

Add Webhook · Write

Add a webhook that receives batches of message events (send, deferral, hard_bounce, soft_bounce, open, click, spam, unsub, reject).
Returns the webhook's id, url, events and auth_key (used to verify signatures).

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `url` (`string`, required): The URL to POST batches of events. Example: https://example.com/mandrill/webhook
- `description` (`string`, optional): An optional description of the webhook. Example: Order events
- `events` (`array`, optional): An optional list of events that will be posted to the webhook. Example: ["send", "hard_bounce", "open", "click"]

Example input: `{"url":"<url>"}`

### `mandrill_webhook_update`

Update Webhook · Write

Change a webhook's URL, description or events.
Returns the updated webhook.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`number`, required): The unique identifier of a webhook belonging to this account. Example: 1
- `url` (`string`, required): The URL to POST batches of events. Requires webhook to exist. Example: https://example.com/mandrill/webhook
- `description` (`string`, optional): An optional description of the webhook. Example: Order events
- `events` (`array`, optional): An optional list of events that will be posted to the webhook. Example: ["send", "hard_bounce"]

Example input: `{"id":1,"url":"<url>"}`

### `mandrill_allowlist_delete`

Remove from Allowlist · Destructive

Remove an address from the allowlist.
Returns email and deleted.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, required): The email address to remove from the allowlist. Example: jane@example.com

Example input: `{"email":"<email>"}`

### `mandrill_inbound_domain_delete`

Delete Inbound Domain · Destructive

Delete an inbound domain and its routes.
Returns the deleted domain.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): An existing inbound domain. Example: mail.example.com

Example input: `{"domain":"<domain>"}`

### `mandrill_inbound_route_delete`

Delete Inbound Route · Destructive

Delete an inbound route.
Returns the deleted route.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique identifier of an existing route. Example: 7.a1b2c3d4e5f6a7b8

Example input: `{"id":"<id>"}`

### `mandrill_metadata_field_delete`

Delete Metadata Field · Destructive

Delete a custom metadata field.
Returns name, state and view_template.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, required): Metadata field name to delete. Example: order_id

Example input: `{"name":"<name>"}`

### `mandrill_reject_delete`

Remove from Denylist · Destructive

Remove an address from the denylist so Mandrill can send to it again.
Returns email and deleted.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, required): An email address. Example: jane@example.com
- `subaccount` (`string`, optional): An optional unique identifier for the subaccount to limit the denylist deletion. Example: cust-123

Example input: `{"email":"<email>"}`

### `mandrill_scheduled_message_cancel`

Cancel Scheduled Message · Destructive

Cancel a scheduled message before it is sent.
Returns the cancelled message's _id, created_at, send_at, from_email, to and subject.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): Scheduled message ID from mandrill_scheduled_messages_list. Example: abc123abc123abc123abc123abc123

Example input: `{"id":"<id>"}`

### `mandrill_sender_domain_delete`

Delete Sender Domain · Destructive

Remove a sending domain from the account.
Returns the deleted domain's details.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The domain name to delete. Example: mail.example.com

Example input: `{"domain":"<domain>"}`

### `mandrill_tag_delete`

Delete Tag · Destructive

Delete a tag and its statistics. Messages are not affected; the tag is recreated if used again.
Returns the deleted tag's statistics.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `tag` (`string`, required): A tag name. Example: password-reset

Example input: `{"tag":"<tag>"}`

### `mandrill_template_delete`

Delete Template · Destructive

Delete a template.
Returns the deleted template.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, required): The immutable name of an existing template. Example: order-shipped

Example input: `{"name":"<name>"}`

### `mandrill_webhook_delete`

Delete Webhook · Destructive

Delete a webhook.
Returns the deleted webhook.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`integer`, required): The unique identifier of a webhook belonging to this account. Example: 1

Example input: `{"id":1}`

## Related

Other Communication connectors ([all 132](/agentkit/connectors/?category=communication)):

- [Gmail](/agentkit/connectors/gmail/): Scalekit connector, OAuth, 48 tools
- [Slack](/agentkit/connectors/slack/): Scalekit connector, OAuth, 96 tools
- [Google Calendar](/agentkit/connectors/googlecalendar/): Scalekit connector, OAuth, 30 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
