> **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 Doppler Marketing Automation

The Doppler Marketing Automation connector lets your AI agent act in each user's Doppler Marketing Automation account. Each user connects their own Doppler Marketing Automation API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 51 tools.

**Authentication:** API Key
**Categories:** Marketing
**Tools:** 51: 30 read, 13 write, 8 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=DOPPLERMARKETING)

## 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 Doppler Marketing Automation connection

   In **AgentKit > Connections**, create a Doppler Marketing Automation 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 = 'dopplermarketing'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Doppler Marketing Automation:', 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: 'dopplermarketing_account_get',
     toolInput: { account_email: 'marketing@acme.com' },
   })
   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 = "dopplermarketing"
   identifier = "user_123"

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

   # Make your first call
   result = actions.execute_tool(
       tool_input={"account_email":"marketing@acme.com"},
       tool_name="dopplermarketing_account_get",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Doppler Marketing Automation 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: 'dopplermarketing_account_get',
  toolInput: {
    account_email: '<account_email>',
  },
  connector: 'dopplermarketing',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="dopplermarketing_account_get",
    tool_input={
        "account_email": "<account_email>",
    },
    connection_name="dopplermarketing",
    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.

### `dopplermarketing_account_get`

Get Account · Read-only

Get the Doppler account's home resource with links to its lists, campaigns, fields and subscribers. Returns the account object. Use it as a connection test that the API key and account email match.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.

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

### `dopplermarketing_automation_deliverability_list`

List Automation Deliverability · Read-only

List an automation's deliverability over a date range (delivered, soft and hard bounces). Returns deliverability records.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `scheduled_task_id` (`integer`, required): Automation (scheduled task) ID, from dopplermarketing_automations_list. Example: 1234567.
- `from` (`string`, optional): Start date of the report period (YYYY-MM-DD). Example: 2026-01-01.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.
- `to` (`string`, optional): End date of the report period (YYYY-MM-DD). Example: 2026-01-31.

Example input: `{"account_email":"<account_email>","scheduled_task_id":1234567}`

### `dopplermarketing_automation_links_list`

List Automation Link Clicks · Read-only

List the links in an automation's emails with their click counts over a date range. Returns link records.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `scheduled_task_id` (`integer`, required): Automation (scheduled task) ID, from dopplermarketing_automations_list. Example: 1234567.
- `from` (`string`, optional): Start date of the report period (YYYY-MM-DD). Example: 2026-01-01.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.
- `to` (`string`, optional): End date of the report period (YYYY-MM-DD). Example: 2026-01-31.

Example input: `{"account_email":"<account_email>","scheduled_task_id":1234567}`

### `dopplermarketing_automation_opens_clicks_list`

List Automation Opens and Clicks · Read-only

List an automation's opens and clicks over a date range, a page at a time. Returns open and click counts by period.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `scheduled_task_id` (`integer`, required): Automation (scheduled task) ID, from dopplermarketing_automations_list. Example: 1234567.
- `from` (`string`, optional): Start date of the report period (YYYY-MM-DD). Example: 2026-01-01.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.
- `to` (`string`, optional): End date of the report period (YYYY-MM-DD). Example: 2026-01-31.

Example input: `{"account_email":"<account_email>","scheduled_task_id":1234567}`

### `dopplermarketing_automation_summary_get`

Get Automation Summary · Read-only

Get an automation's delivery, open and bounce rates for a date range. Returns the summary report.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `scheduled_task_id` (`integer`, required): Automation (scheduled task) ID, from dopplermarketing_automations_list. Example: 1234567.
- `from` (`string`, optional): Start date of the report period (YYYY-MM-DD). Example: 2026-01-01.
- `to` (`string`, optional): End date of the report period (YYYY-MM-DD). Example: 2026-01-31.

Example input: `{"account_email":"<account_email>","scheduled_task_id":1234567}`

### `dopplermarketing_automation_unsubscribes_list`

List Automation Unsubscribes · Read-only

List unsubscribes caused by an automation over a date range. Returns unsubscribe records.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `scheduled_task_id` (`integer`, required): Automation (scheduled task) ID, from dopplermarketing_automations_list. Example: 1234567.
- `from` (`string`, optional): Start date of the report period (YYYY-MM-DD). Example: 2026-01-01.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.
- `to` (`string`, optional): End date of the report period (YYYY-MM-DD). Example: 2026-01-31.

Example input: `{"account_email":"<account_email>","scheduled_task_id":1234567}`

### `dopplermarketing_automations_list`

List Automations · Read-only

List the account's automations (scheduled tasks such as welcome or birthday flows). Returns automation IDs, names and states. Use the IDs with the automation report tools.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.

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

### `dopplermarketing_campaign_content_get`

Get Campaign Content · Read-only

Get the HTML content of a campaign. Returns the HTML.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_deliveries_list`

List Campaign Deliveries · Read-only

List per-subscriber delivery details of a sent campaign (delivered, opened, clicked, bounced), a page at a time. Returns delivery records.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.
- `continuation_token` (`integer`, optional): Token from the previous page to continue the listing. Example: 0.
- `order_by` (`string`, optional): Sort order of the deliveries. Example: interactionDate. One of: `subcriber`, `interactionDate`.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_get`

Get Campaign · Read-only

Get one campaign by ID with its name, sender, subject, state and scheduled date. Returns the campaign object.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_preview_get`

Get Campaign Preview · Read-only

Get a preview of a campaign: a URL to its rendered content and thumbnail. Returns the preview links.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_recipients_get`

Get Campaign Recipients · Read-only

Get the lists and segments a campaign is sent to. Returns lists and segments with IDs and names.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_results_summary_get`

Get Campaign Results Summary · Read-only

Get the results of a sent campaign: recipients, deliveries, opens, clicks, bounces and unsubscribes. Returns the summary.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_shipping_get`

Get Campaign Shipping · Read-only

Get the status of a campaign send or scheduled send. Returns the shipping with type, scheduled date and status.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.
- `shipping_id` (`string`, required): Shipping ID returned by dopplermarketing_campaign_send. Example: SHP-778899.

Example input: `{"account_email":"<account_email>","campaign_id":8765432,"shipping_id":"<shipping_id>"}`

### `dopplermarketing_campaign_social_media_get`

Get Campaign Social Settings · Read-only

Get a campaign's social sharing settings (share and like buttons, Facebook, X, LinkedIn and RSS posting). Returns the settings.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_text_alternative_get`

Get Campaign Plain Text · Read-only

Get the plain-text alternative of a campaign's content. Returns the text.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_unsubscribed_list`

List Campaign Unsubscribes · Read-only

List the subscribers who unsubscribed through a campaign in a date range. Returns emails and dates.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.
- `from` (`string`, optional): Start date of the report period (YYYY-MM-DD). Example: 2026-01-01.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.
- `to` (`string`, optional): End date of the report period (YYYY-MM-DD). Example: 2026-01-31.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaigns_list`

List Campaigns · Read-only

List email campaigns, optionally by state (draft, scheduled, shipping, shipped) or scheduled date range, a page at a time. Returns campaign IDs, names, subjects and states. Use dopplermarketing_campaign_get for one campaign.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.
- `scheduled_date_from` (`string`, optional): Only campaigns scheduled on or after this date. Example: 2026-01-01.
- `scheduled_date_to` (`string`, optional): Only campaigns scheduled on or before this date. Example: 2026-03-31.
- `state` (`string`, optional): Filter by campaign state. Example: draft. One of: `draft`, `scheduled`, `shipping`, `shipped`.

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

### `dopplermarketing_fields_list`

List Fields · Read-only

List the subscriber fields of the account, both predefined (FIRSTNAME, LASTNAME, BIRTHDAY, ...) and custom. Returns field names, types and whether they are required or private. Use the names in the fields input of subscriber tools.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.

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

### `dopplermarketing_list_get`

Get Subscriber List · Read-only

Get one subscriber list by ID. Returns the list with its name, status and subscriber count.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `list_id` (`integer`, required): Subscriber list ID, from dopplermarketing_lists_list. Example: 509702.

Example input: `{"account_email":"<account_email>","list_id":509702}`

### `dopplermarketing_list_subscribers_list`

List Subscribers in List · Read-only

List the subscribers of one list, up to 100 per page. Returns subscribers with email, fields and status. Use dopplermarketing_subscribers_list for the whole account.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `list_id` (`integer`, required): Subscriber list ID, from dopplermarketing_lists_list. Example: 509702.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.

Example input: `{"account_email":"<account_email>","list_id":509702}`

### `dopplermarketing_lists_list`

List Subscriber Lists · Read-only

List the account's subscriber lists, optionally by state or name, a page at a time. Returns list IDs, names, subscriber counts and creation dates.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `list_name` (`string`, optional): Filter by list name. Example: Newsletter.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.
- `state` (`string`, optional): Filter by list state. Example: active. One of: `active`, `inactive`, `all`.

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

### `dopplermarketing_subscriber_deliveries_list`

List Subscriber Deliveries · Read-only

List the campaigns sent to one subscriber with delivery, open and click details. Returns delivery records, a page at a time.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `email` (`string`, required): Subscriber email address. Example: jane.doe@example.com.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.

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

### `dopplermarketing_subscriber_get`

Get Subscriber · Read-only

Get one subscriber by email with their field values, lists and status. Returns the subscriber object.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `email` (`string`, required): Subscriber email address. Example: jane.doe@example.com.

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

### `dopplermarketing_subscriber_permission_history_list`

List Subscriber Permission History · Read-only

List the history of changes to one permission (consent) field of a subscriber, with date, origin IP and value. Returns history records.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `email` (`string`, required): Subscriber email address. Example: jane.doe@example.com.
- `field_name` (`string`, required): Name of the permission field. Example: CONSENT_NEWSLETTER.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.

Example input: `{"account_email":"<account_email>","email":"<email>","field_name":"<field_name>"}`

### `dopplermarketing_subscribers_list`

List Subscribers · Read-only

List the account's subscribers across all lists, up to 100 per page, optionally searched by keyword or updated since a date. Returns subscribers with email, fields and status. Use dopplermarketing_subscriber_get for one subscriber.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `keyword` (`string`, optional): Search text matched against subscriber email and fields. Example: jane.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.
- `resume_from` (`integer`, optional): Subscriber ID to resume a large listing from. Example: 0.
- `updated_after` (`string`, optional): Only subscribers updated after this ISO 8601 time. Example: 2026-01-01T00:00:00Z.
- `with_field_type` (`string`, optional): Only include fields of this type, for example permission. Example: permission.

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

### `dopplermarketing_task_get`

Get Task · Read-only

Get one asynchronous task (for example an import) with its status and progress. Returns the task object.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `task_id` (`string`, required): Task ID returned by an import, from dopplermarketing_tasks_list. Example: a1b2c3d4-import.

Example input: `{"account_email":"<account_email>","task_id":"<task_id>"}`

### `dopplermarketing_task_import_errors_list`

List Import Errors · Read-only

List the rows an import task could not import, with the reason for each. Returns error records, a page at a time.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `task_id` (`string`, required): Task ID returned by an import, from dopplermarketing_tasks_list. Example: a1b2c3d4-import.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.

Example input: `{"account_email":"<account_email>","task_id":"<task_id>"}`

### `dopplermarketing_tasks_list`

List Tasks · Read-only

List the account's asynchronous tasks, such as subscriber imports. Returns task IDs, types, statuses and dates.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.

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

### `dopplermarketing_unsubscribed_list`

List Unsubscribed · Read-only

List subscribers removed from the account (unsubscribes, bounces, manual removals) in a date range, up to 100 per page. Returns emails with the removal type and date.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `from` (`string`, optional): Start date of the report period (YYYY-MM-DD). Example: 2026-01-01.
- `page` (`integer`, optional): Page number of results, starting at 1. Example: 1.
- `per_page` (`integer`, optional): Number of results per page. Example: 20.
- `to` (`string`, optional): End date of the report period (YYYY-MM-DD). Example: 2026-01-31.

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

### `dopplermarketing_campaign_approve`

Approve Campaign · Write

Approve a campaign that is waiting for approval before sending. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_create`

Create Campaign Draft · Write

Create a campaign draft with name, sender name and email, and subject. Returns the new campaign ID. Then set recipients with dopplermarketing_campaign_recipients_update, add content in the Doppler editor, and send with dopplermarketing_campaign_send.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `from_email` (`string`, required): Sender email address; it must be a verified sender in Doppler. Example: news@acme.com.
- `from_name` (`string`, required): Sender name shown to subscribers. Example: Acme Marketing.
- `name` (`string`, required): Internal name of the campaign. Example: February newsletter.
- `subject` (`string`, required): Email subject line. Example: What's new at Acme in February.
- `content_required` (`boolean`, optional): Set to true to require content before sending. Example: true.
- `preheader` (`string`, optional): Preview text shown after the subject. Example: Three new features and a customer story.
- `recipients_required` (`boolean`, optional): Set to true to require recipients before sending. Example: true.
- `reply_to` (`string`, optional): Reply-to email address. Example: support@acme.com.
- `text_campaign` (`boolean`, optional): Set to true for a plain-text campaign. Example: false.

Example input: `{"account_email":"<account_email>","from_email":"<from_email>","from_name":"<from_name>","name":"<name>","subject":"<subject>"}`

### `dopplermarketing_campaign_recipients_update`

Update Campaign Recipients · Write

Set the lists and/or segments a campaign is sent to, replacing the current ones. Returns the result. Get list IDs from dopplermarketing_lists_list.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.
- `lists` (`array`, optional): Subscriber lists to send to, each as an object with id. Example: [{"id": 509702}]
- `segments` (`array`, optional): Segments to send to, each as an object with id. Example: [{"id": 1200}]

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_send`

Send or Schedule Campaign · Write

Send a campaign now (type immediate) or schedule it (type scheduled with scheduled_date). Returns the shipping with its ID. This emails every recipient; check recipients and content first.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.
- `type` (`string`, required): immediate to send now, scheduled to send at scheduled_date. Example: scheduled. One of: `immediate`, `scheduled`.
- `scheduled_date` (`string`, optional): Date and time to send, in ISO 8601 format; required when type is scheduled. Example: 2026-02-01T14:00:00Z.

Example input: `{"account_email":"<account_email>","campaign_id":8765432,"type":"immediate"}`

### `dopplermarketing_campaign_text_alternative_update`

Update Campaign Plain Text · Write

Set the plain-text alternative shown by mail clients that cannot display HTML. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.
- `text` (`string`, required): Plain-text version of the campaign content. Example: Hi, here is our February newsletter. Read it online at https://acme.com/news.

Example input: `{"account_email":"<account_email>","campaign_id":8765432,"text":"<text>"}`

### `dopplermarketing_campaign_update`

Update Campaign · Write

Update a draft campaign's name, sender, subject, preheader or reply-to. Returns the result. Only drafts can be changed.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.
- `from_email` (`string`, required): Sender email address; it must be a verified sender in Doppler. Example: news@acme.com.
- `from_name` (`string`, required): Sender name shown to subscribers. Example: Acme Marketing.
- `name` (`string`, required): Internal name of the campaign. Example: February newsletter.
- `subject` (`string`, required): Email subject line. Example: What's new at Acme in February.
- `content_required` (`boolean`, optional): Set to true to require content before sending. Example: true.
- `preheader` (`string`, optional): Preview text shown after the subject. Example: Three new features and a customer story.
- `recipients_required` (`boolean`, optional): Set to true to require recipients before sending. Example: true.
- `reply_to` (`string`, optional): Reply-to email address. Example: support@acme.com.
- `text_campaign` (`boolean`, optional): Set to true for a plain-text campaign. Example: false.

Example input: `{"account_email":"<account_email>","campaign_id":8765432,"from_email":"<from_email>","from_name":"<from_name>","name":"<name>","subject":"<subject>"}`

### `dopplermarketing_list_create`

Create Subscriber List · Write

Create a subscriber list with a unique name. Returns the new list ID. Add subscribers with dopplermarketing_list_subscriber_add or dopplermarketing_list_subscribers_import.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `name` (`string`, required): Name of the list, unique in the account. Example: February newsletter.
- `current_status` (`string`, optional): Current Status. Example: ready. One of: `ready`, `draft`, `readyToSent`, `sent`, `importingSubscribers`, `exportingSubscribers`, `mergingDestination`, `mergingSource`, `cancelingExportingSubscribers`, `inCreationProcess`, `sending`, `inDeletingProcess`, `deleted`, `blocked`.

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

### `dopplermarketing_list_subscriber_add`

Add Subscriber to List · Write

Add a subscriber to a list by email with optional field values, creating the subscriber if needed. Returns the result. Use dopplermarketing_list_subscribers_import for many at once, or dopplermarketing_list_subscriber_double_optin_add to send a confirmation email first.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `email` (`string`, required): Subscriber email address. Example: jane.doe@example.com.
- `list_id` (`integer`, required): Subscriber list ID, from dopplermarketing_lists_list. Example: 509702.
- `allow_re_subscription` (`boolean`, optional): Set to true to re-add a subscriber who had unsubscribed. Example: false.
- `fields` (`array`, optional): Custom field values, each an object with name and value (for example FIRSTNAME, LASTNAME, BIRTHDAY), from dopplermarketing_fields_list. Example: [{"name": "FIRSTNAME", "value": "Jane"}, {"name": "LASTNAME", "value": "Doe"}]
- `manual_unsubscription_reason` (`string`, optional): Reason for a manual removal. Example: administrative. One of: `administrative`, `subscriberRequestNeverSubscribed`, `subscriberRequestNotInterestingContent`, `subscriberRequestIsSpam`, `subscriberRequestTooManyEmails`, `subscriberRequestOther`.
- `status` (`string`, optional): Status. Example: active. One of: `active`, `pending`, `unsubscribed`, `standBy`, `archived`.
- `unsubscription_comment` (`string`, optional): Free-text comment about the removal. Example: Requested by phone.
- `unsubscription_type` (`string`, optional): Why the subscriber is removed. Example: manual. One of: `hardBounce`, `softBounce`, `neverOpen`, `abuseLink`, `feedbackLoop`, `internalPolicies`, `manual`.

Example input: `{"account_email":"<account_email>","email":"<email>","list_id":509702}`

### `dopplermarketing_list_subscriber_double_optin_add`

Add Subscriber with Double Opt-In · Write

Add a subscriber to a list through double opt-in: Doppler emails a confirmation from the given template and adds them once they confirm. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `email` (`string`, required): Subscriber email address. Example: jane.doe@example.com.
- `list_id` (`integer`, required): Subscriber list ID, from dopplermarketing_lists_list. Example: 509702.
- `template_id` (`integer`, required): Double opt-in template ID. Example: 4321.
- `fields` (`array`, optional): Custom field values, each an object with name and value (for example FIRSTNAME, LASTNAME, BIRTHDAY), from dopplermarketing_fields_list. Example: [{"name": "FIRSTNAME", "value": "Jane"}, {"name": "LASTNAME", "value": "Doe"}]
- `manual_unsubscription_reason` (`string`, optional): Reason for a manual removal. Example: administrative. One of: `administrative`, `subscriberRequestNeverSubscribed`, `subscriberRequestNotInterestingContent`, `subscriberRequestIsSpam`, `subscriberRequestTooManyEmails`, `subscriberRequestOther`.
- `status` (`string`, optional): Status. Example: active. One of: `active`, `pending`, `unsubscribed`, `standBy`, `archived`.
- `unsubscription_comment` (`string`, optional): Free-text comment about the removal. Example: Requested by phone.
- `unsubscription_type` (`string`, optional): Why the subscriber is removed. Example: manual. One of: `hardBounce`, `softBounce`, `neverOpen`, `abuseLink`, `feedbackLoop`, `internalPolicies`, `manual`.

Example input: `{"account_email":"<account_email>","email":"<email>","list_id":509702,"template_id":4321}`

### `dopplermarketing_list_subscribers_import`

Import Subscribers to List · Write

Import many subscribers into a list in one asynchronous task, listing the field names sent for each. Returns a task ID; check it with dopplermarketing_task_get and dopplermarketing_task_import_errors_list.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `fields` (`array`, required): Names of the fields included in each item, for example ["FIRSTNAME", "LASTNAME"]. Example: ["FIRSTNAME", "LASTNAME"]
- `items` (`array`, required): Subscribers to import, each with email and fields. Example: [{"email": "jane.doe@example.com", "fields": [{"name": "FIRSTNAME", "value": "Jane"}]}]
- `list_id` (`integer`, required): Subscriber list ID, from dopplermarketing_lists_list. Example: 509702.
- `callback` (`string`, optional): URL Doppler calls when the import finishes. Example: https://example.com/hooks/doppler-import.
- `enable_email_notification` (`boolean`, optional): Set to true to email the account when the import finishes. Example: false.

Example input: `{"account_email":"<account_email>","fields":["FIRSTNAME","LASTNAME"],"items":[{"email":"jane.doe@example.com"}],"list_id":509702}`

### `dopplermarketing_list_update`

Rename Subscriber List · Write

Rename a subscriber list. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `list_id` (`integer`, required): Subscriber list ID, from dopplermarketing_lists_list. Example: 509702.
- `name` (`string`, required): New name of the list. Example: February newsletter.
- `current_status` (`string`, optional): Current Status. Example: ready. One of: `ready`, `draft`, `readyToSent`, `sent`, `importingSubscribers`, `exportingSubscribers`, `mergingDestination`, `mergingSource`, `cancelingExportingSubscribers`, `inCreationProcess`, `sending`, `inDeletingProcess`, `deleted`, `blocked`.

Example input: `{"account_email":"<account_email>","list_id":509702,"name":"<name>"}`

### `dopplermarketing_subscriber_create`

Create Subscriber · Write

Create or update a subscriber in the account, without adding them to a list, with optional field values. Returns the result. Use dopplermarketing_list_subscriber_add to put them in a list.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `email` (`string`, required): Subscriber email address. Example: jane.doe@example.com.
- `fields` (`array`, optional): Custom field values, each an object with name and value (for example FIRSTNAME, LASTNAME, BIRTHDAY), from dopplermarketing_fields_list. Example: [{"name": "FIRSTNAME", "value": "Jane"}, {"name": "LASTNAME", "value": "Doe"}]
- `manual_unsubscription_reason` (`string`, optional): Reason for a manual removal. Example: administrative. One of: `administrative`, `subscriberRequestNeverSubscribed`, `subscriberRequestNotInterestingContent`, `subscriberRequestIsSpam`, `subscriberRequestTooManyEmails`, `subscriberRequestOther`.
- `status` (`string`, optional): Status. Example: active. One of: `active`, `pending`, `unsubscribed`, `standBy`, `archived`.
- `unsubscription_comment` (`string`, optional): Free-text comment about the removal. Example: Requested by phone.
- `unsubscription_type` (`string`, optional): Why the subscriber is removed. Example: manual. One of: `hardBounce`, `softBounce`, `neverOpen`, `abuseLink`, `feedbackLoop`, `internalPolicies`, `manual`.

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

### `dopplermarketing_subscribers_import`

Import Subscribers · Write

Import many subscribers into the account in one asynchronous task. Returns a task ID; check it with dopplermarketing_task_get.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `fields` (`array`, required): Names of the fields included in each item, for example ["FIRSTNAME", "LASTNAME"]. Example: ["FIRSTNAME", "LASTNAME"]
- `items` (`array`, required): Subscribers to import, each with email and fields. Example: [{"email": "jane.doe@example.com", "fields": [{"name": "FIRSTNAME", "value": "Jane"}]}]
- `callback` (`string`, optional): URL Doppler calls when the import finishes. Example: https://example.com/hooks/doppler-import.
- `enable_email_notification` (`boolean`, optional): Set to true to email the account when the import finishes. Example: false.

Example input: `{"account_email":"<account_email>","fields":["FIRSTNAME","LASTNAME"],"items":[{"email":"jane.doe@example.com"}]}`

### `dopplermarketing_campaign_delete`

Delete Campaign · Destructive

Delete a campaign. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_campaign_shipping_cancel`

Cancel Scheduled Campaign · Destructive

Cancel a scheduled campaign send before it goes out. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.
- `shipping_id` (`string`, required): Shipping ID returned by dopplermarketing_campaign_send. Example: SHP-778899.

Example input: `{"account_email":"<account_email>","campaign_id":8765432,"shipping_id":"<shipping_id>"}`

### `dopplermarketing_campaign_text_alternative_delete`

Delete Campaign Plain Text · Destructive

Remove a campaign's plain-text alternative. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `campaign_id` (`integer`, required): Campaign ID, from dopplermarketing_campaigns_list. Example: 8765432.

Example input: `{"account_email":"<account_email>","campaign_id":8765432}`

### `dopplermarketing_list_delete`

Delete Subscriber List · Destructive

Delete a subscriber list. Its subscribers stay in the account. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `list_id` (`integer`, required): Subscriber list ID, from dopplermarketing_lists_list. Example: 509702.

Example input: `{"account_email":"<account_email>","list_id":509702}`

### `dopplermarketing_list_subscriber_remove`

Remove Subscriber from List · Destructive

Remove a subscriber from one list. The subscriber stays in the account and in other lists. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `email` (`string`, required): Subscriber email address. Example: jane.doe@example.com.
- `list_id` (`integer`, required): Subscriber list ID, from dopplermarketing_lists_list. Example: 509702.

Example input: `{"account_email":"<account_email>","email":"<email>","list_id":509702}`

### `dopplermarketing_subscriber_archive`

Archive Subscriber · Destructive

Archive a subscriber so they are hidden from lists and campaigns. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `email` (`string`, required): Subscriber email address. Example: jane.doe@example.com.

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

### `dopplermarketing_subscriber_unsubscribe`

Unsubscribe Subscriber · Destructive

Remove a subscriber from the whole account so they receive no more campaigns, with a removal type and reason. Returns the result.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `email` (`string`, required): Subscriber email address. Example: jane.doe@example.com.
- `fields` (`array`, optional): Custom field values, each an object with name and value (for example FIRSTNAME, LASTNAME, BIRTHDAY), from dopplermarketing_fields_list. Example: [{"name": "FIRSTNAME", "value": "Jane"}, {"name": "LASTNAME", "value": "Doe"}]
- `manual_unsubscription_reason` (`string`, optional): Reason for a manual removal. Example: administrative. One of: `administrative`, `subscriberRequestNeverSubscribed`, `subscriberRequestNotInterestingContent`, `subscriberRequestIsSpam`, `subscriberRequestTooManyEmails`, `subscriberRequestOther`.
- `status` (`string`, optional): Status. Example: active. One of: `active`, `pending`, `unsubscribed`, `standBy`, `archived`.
- `unsubscription_comment` (`string`, optional): Free-text comment about the removal. Example: Requested by phone.
- `unsubscription_type` (`string`, optional): Why the subscriber is removed. Example: manual. One of: `hardBounce`, `softBounce`, `neverOpen`, `abuseLink`, `feedbackLoop`, `internalPolicies`, `manual`.

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

### `dopplermarketing_unsubscribed_import`

Import Unsubscribed · Destructive

Unsubscribe many emails from the account in one asynchronous task. Returns a task ID; check it with dopplermarketing_task_get.

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

Inputs:

- `account_email` (`string`, required): Email address of your Doppler account (the account the API key belongs to). Example: marketing@acme.com.
- `items` (`array`, required): Subscribers to unsubscribe, each with email. Example: [{"email": "jane.doe@example.com"}]

Example input: `{"account_email":"<account_email>","items":[{"email":"jane.doe@example.com"}]}`

## Related

Other Marketing connectors ([all 190](/agentkit/connectors/?category=marketing)):

- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Mailchimp](/agentkit/connectors/mailchimp/): Scalekit connector, OAuth, 73 tools
- [Twitter / X](/agentkit/connectors/twitteroauth/): Scalekit connector, OAuth, 92 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 |
