> **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 ActiveTrail

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

**Authentication:** API Key
**Categories:** Marketing, Communication
**Tools:** 60: 38 read, 15 write, 7 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=ACTIVETRAIL)

## 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 ActiveTrail connection

   In **AgentKit > Connections**, create an ActiveTrail 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 = 'activetrail'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize ActiveTrail:', 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: 'activetrail_account_balance_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 = "activetrail"
   identifier = "user_123"

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

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

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their ActiveTrail 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: 'activetrail_account_balance_get',
  toolInput: {},
  connector: 'activetrail',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="activetrail_account_balance_get",
    tool_input={},
    connection_name="activetrail",
    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.

### `activetrail_account_balance_get`

Get Account Balance · Read-only

Get the email and SMS credit balance of the ActiveTrail account.
Returns the remaining email and SMS credits.
Use this before sending large campaigns.

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

Inputs: none.

Example input: `{}`

### `activetrail_automation_activation_get`

Get Automation Activation · Read-only

Get whether an ActiveTrail automation is published (active).
Returns is_published and any scheduled activation time.
Use this before activating or pausing it.

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

Inputs:

- `automation_id` (`integer`, required): Automation ID, from activetrail_automations_list. Example: 7788.

Example input: `{"automation_id":7788}`

### `activetrail_automation_get`

Get Automation · Read-only

Get the details of an ActiveTrail automation, without its steps.
Returns the automation's name, state, trigger and settings.
Use this for an automation's details.

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

Inputs:

- `automation_id` (`integer`, required): Automation ID, from activetrail_automations_list. Example: 7788.

Example input: `{"automation_id":7788}`

### `activetrail_automation_summary_report_get`

Get Automation Summary Report · Read-only

Get the summary report of the email campaigns inside an ActiveTrail automation.
Returns per-email sent, opens, clicks, bounces and unsubscribes.
Use this to measure an automation.

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

Inputs:

- `automation_id` (`integer`, required): Automation ID, from activetrail_automations_list. Example: 7788.
- `bots` (`boolean`, optional): True includes opens and clicks detected as bots. Example: false.
- `from_date` (`string`, optional): Start date, YYYY-MM-DD. Example: 2026-10-01.
- `to_date` (`string`, optional): End date, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{"automation_id":7788}`

### `activetrail_automations_list`

List Automations · Read-only

List the automations of the ActiveTrail account, optionally by state.
Returns automations with ID, name, state and dates.
Use this to find automation IDs.

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

Inputs:

- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `state_type` (`integer`, optional): State filter: 5 untitled, 10 draft, 15 paused, 20 published, 30 deleted. Example: 20. One of: `5`, `10`, `15`, `20`, `30`.

Example input: `{}`

### `activetrail_campaign_get`

Get Email Campaign · Read-only

Get one ActiveTrail email campaign with its details, design, segment and scheduling.
Returns the full campaign.
Use this to inspect a campaign. Use activetrail_campaign_report_get for its results.

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

Inputs:

- `campaign_id` (`integer`, required): Email campaign ID, from activetrail_sent_campaigns_list or activetrail_campaign_reports_list. Example: 987654.

Example input: `{"campaign_id":987654}`

### `activetrail_campaign_report_activity_list`

List Campaign Email Activity · Read-only

List every contact's activity on an ActiveTrail email campaign.
Returns per-contact sent, open, click, bounce and unsubscribe flags.
Use this for a full per-contact export of one campaign.

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

Inputs:

- `campaign_id` (`integer`, required): Email campaign ID, from activetrail_sent_campaigns_list or activetrail_campaign_reports_list. Example: 987654.
- `from_date` (`string`, optional): Start of the last update date range, YYYY-MM-DD. Example: 2026-10-01.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `to_date` (`string`, optional): End of the last update date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{"campaign_id":987654}`

### `activetrail_campaign_report_bounces_list`

List Campaign Bounces · Read-only

List the bounces of an ActiveTrail email campaign and the bounce count per domain.
Returns bounced contacts with bounce type and per-domain totals.
Use this to clean bad addresses.

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

Inputs:

- `campaign_id` (`integer`, required): Email campaign ID, from activetrail_sent_campaigns_list or activetrail_campaign_reports_list. Example: 987654.
- `from_date` (`string`, optional): Start of the last update date range, YYYY-MM-DD. Example: 2026-10-01.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `to_date` (`string`, optional): End of the last update date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{"campaign_id":987654}`

### `activetrail_campaign_report_clicks_list`

List Campaign Clicks · Read-only

List the link clicks of an ActiveTrail email campaign.
Returns links with click counts and the contacts who clicked.
Use this to see which links worked.

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

Inputs:

- `campaign_id` (`integer`, required): Email campaign ID, from activetrail_sent_campaigns_list or activetrail_campaign_reports_list. Example: 987654.
- `from_date` (`string`, optional): Start of the last update date range, YYYY-MM-DD. Example: 2026-10-01.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `to_date` (`string`, optional): End of the last update date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{"campaign_id":987654}`

### `activetrail_campaign_report_get`

Get Email Campaign Report · Read-only

Get the overview report of one ActiveTrail email campaign.
Returns sent, opens, clicks, bounces, unsubscribes and complaints with rates.
Use this for one campaign's results. Use the campaign_report_* tools for the contacts behind each number.

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

Inputs:

- `campaign_id` (`integer`, required): Email campaign ID, from activetrail_sent_campaigns_list or activetrail_campaign_reports_list. Example: 987654.
- `from_date` (`string`, optional): Start of the last update date range, YYYY-MM-DD. Example: 2026-10-01.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `to_date` (`string`, optional): End of the last update date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{"campaign_id":987654}`

### `activetrail_campaign_report_opens_list`

List Campaign Openers · Read-only

List the contacts who opened an ActiveTrail email campaign, optionally from one group.
Returns openers with email, name and open time.
Use this to follow up with engaged contacts.

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

Inputs:

- `campaign_id` (`integer`, required): Email campaign ID, from activetrail_sent_campaigns_list or activetrail_campaign_reports_list. Example: 987654.
- `from_date` (`string`, optional): Start of the last update date range, YYYY-MM-DD. Example: 2026-10-01.
- `group_id` (`integer`, optional): Only openers from this group. Example: 45678.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `to_date` (`string`, optional): End of the last update date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{"campaign_id":987654}`

### `activetrail_campaign_report_sent_list`

List Campaign Recipients · Read-only

List the contacts an ActiveTrail email campaign was sent to, optionally from one group.
Returns recipients with email and send time.
Use this to see who received a campaign.

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

Inputs:

- `campaign_id` (`integer`, required): Email campaign ID, from activetrail_sent_campaigns_list or activetrail_campaign_reports_list. Example: 987654.
- `from_date` (`string`, optional): Start of the last update date range, YYYY-MM-DD. Example: 2026-10-01.
- `group_id` (`integer`, optional): Only recipients from this group. Example: 45678.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `to_date` (`string`, optional): End of the last update date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{"campaign_id":987654}`

### `activetrail_campaign_report_unsubscribed_list`

List Campaign Unsubscribes · Read-only

List the contacts who unsubscribed from an ActiveTrail email campaign.
Returns contacts with email and unsubscribe time.
Use this to sync opt-outs from one campaign.

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

Inputs:

- `campaign_id` (`integer`, required): Email campaign ID, from activetrail_sent_campaigns_list or activetrail_campaign_reports_list. Example: 987654.
- `from_date` (`string`, optional): Start of the last update date range, YYYY-MM-DD. Example: 2026-10-01.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `to_date` (`string`, optional): End of the last update date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{"campaign_id":987654}`

### `activetrail_campaign_reports_list`

List Email Campaign Reports · Read-only

List report summaries of ActiveTrail email campaigns: send date, opens, clicks, click-to-open, bounces, unsubscribes, complaints and unopened.
Returns one row per campaign.
Use this to compare campaigns. Use activetrail_campaign_report_get for one campaign.

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

Inputs:

- `from_date` (`string`, optional): Start of the last update date range, YYYY-MM-DD. Example: 2026-10-01.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `to_date` (`string`, optional): End of the last update date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{}`

### `activetrail_campaign_scheduling_get`

Get Email Campaign Schedule · Read-only

Get when an ActiveTrail email campaign is or was sent.
Returns is_sent and the scheduled UTC date.
Use this to check a campaign's send time.

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

Inputs:

- `campaign_id` (`integer`, required): Email campaign ID, from activetrail_sent_campaigns_list or activetrail_campaign_reports_list. Example: 987654.

Example input: `{"campaign_id":987654}`

### `activetrail_contact_activity_list`

List Contact Activity · Read-only

List an ActiveTrail contact's activity on the emails sent to them.
Returns campaigns with sent, open, click, bounce and unsubscribe events.
Use this to see how a contact engages.

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

Inputs:

- `contact_id` (`integer`, required): Contact ID, from activetrail_contacts_list. Example: 123456.

Example input: `{"contact_id":123456}`

### `activetrail_contact_fields_list`

List Contact Fields · Read-only

List the contact fields of the ActiveTrail account, including what each custom ext field is used for.
Returns fields with name, display name and type.
Use this to map custom data to ext1..ext25 before creating contacts.

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

Inputs:

- `fields_type` (`integer`, optional): Only fields of this type: 1 text, 2 number, 3 boolean, 4 date, 5 email, 6 mobile, 7 contact and order. Example: 1. One of: `1`, `2`, `3`, `4`, `5`, `6`, `7`.

Example input: `{}`

### `activetrail_contact_get`

Get Contact · Read-only

Get one ActiveTrail contact.
Returns the contact's email, mobile, name, statuses, dates and custom fields.
Use this for a contact's details. Use activetrail_contact_activity_list for their email activity.

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

Inputs:

- `contact_id` (`integer`, required): Contact ID, from activetrail_contacts_list. Example: 123456.

Example input: `{"contact_id":123456}`

### `activetrail_contact_groups_list`

List Contact Groups · Read-only

List the groups an ActiveTrail contact belongs to.
Returns groups with ID and name.
Use this to check a contact's group memberships.

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

Inputs:

- `contact_id` (`integer`, required): Contact ID, from activetrail_contacts_list. Example: 123456.

Example input: `{"contact_id":123456}`

### `activetrail_contact_mailing_lists_list`

List Contact Mailing Lists · Read-only

List the mailing lists an ActiveTrail contact belongs to.
Returns mailing lists with ID and name.
Use this to check a contact's mailing list memberships.

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

Inputs:

- `contact_id` (`integer`, required): Contact ID, from activetrail_contacts_list. Example: 123456.

Example input: `{"contact_id":123456}`

### `activetrail_contacts_list`

List Contacts · Read-only

List the contacts of the ActiveTrail account, filtered by status, search text or status-change dates.
Returns contacts with ID, email, mobile, name, statuses and fields.
Use this to find contacts. Use activetrail_contact_get for one contact.

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

Inputs:

- `customer_states` (`integer`, optional): Contact status filter as a number: -1 all, -2 active, -3 inactive, 1 unsubscribed by request, 2 bounced, 3 spam complaint, 4 quarantined. Example: -2. One of: `-1`, `-2`, `-3`, `1`, `2`, `3`, `4`.
- `from_date` (`string`, optional): Start of the status change date range, YYYY-MM-DD. Example: 2026-10-01.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `search_term` (`string`, optional): Email or mobile number to search for (emails containing + cannot be searched). Example: jane@example.com.
- `to_date` (`string`, optional): End of the status change date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{}`

### `activetrail_group_get`

Get Group · Read-only

Get one ActiveTrail group.
Returns the group with name, active and total contact counts and dates.
Use this for a group's details.

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

Inputs:

- `group_id` (`integer`, required): Group ID, from activetrail_groups_list or the group's URL in ActiveTrail (Contacts > Groups). Example: 45678.

Example input: `{"group_id":45678}`

### `activetrail_group_members_list`

List Group Members · Read-only

List the contacts in an ActiveTrail group, filtered by status, search text or status-change dates.
Returns contacts with ID, email, mobile, name and statuses.
Use this to read a group. Use activetrail_contacts_list for the whole account.

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

Inputs:

- `group_id` (`integer`, required): Group ID, from activetrail_groups_list or the group's URL in ActiveTrail (Contacts > Groups). Example: 45678.
- `customer_states` (`integer`, optional): Contact status filter as a number: -1 all, -2 active, -3 inactive, 1 unsubscribed by request, 2 bounced, 3 spam complaint, 4 quarantined. Example: -2. One of: `-1`, `-2`, `-3`, `1`, `2`, `3`, `4`.
- `from_date` (`string`, optional): Start of the status change date range, YYYY-MM-DD. Example: 2026-10-01.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `search_term` (`string`, optional): Email or mobile number to search for. Example: jane@example.com.
- `to_date` (`string`, optional): End of the status change date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{"group_id":45678}`

### `activetrail_groups_list`

List Groups · Read-only

List the contact groups of the ActiveTrail account, optionally by name.
Returns groups with ID, name, active and total counters and creation date.
Use this to find group IDs. Use activetrail_group_members_list for a group's contacts.

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

Inputs:

- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `search_term` (`string`, optional): Group name to search for. Example: Newsletter.

Example input: `{}`

### `activetrail_mailing_list_get`

Get Mailing List · Read-only

Get one ActiveTrail mailing list.
Returns the mailing list with ID and name.
Use this for a mailing list's details.

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

Inputs:

- `mailing_list_id` (`integer`, required): Mailing list ID, from activetrail_mailing_lists_list. Example: 3456.

Example input: `{"mailing_list_id":3456}`

### `activetrail_mailing_list_members_list`

List Mailing List Members · Read-only

List the contacts in an ActiveTrail mailing list, filtered by status or status-change dates.
Returns contacts with ID, email, mobile, name and statuses.
Use this to read a mailing list.

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

Inputs:

- `mailing_list_id` (`integer`, required): Mailing list ID, from activetrail_mailing_lists_list. Example: 3456.
- `customer_states` (`integer`, optional): Contact status filter as a number: -1 all, -2 active, -3 inactive, 1 unsubscribed by request, 2 bounced, 3 spam complaint, 4 quarantined. Example: -2. One of: `-1`, `-2`, `-3`, `1`, `2`, `3`, `4`.
- `from_date` (`string`, optional): Start of the status change date range, YYYY-MM-DD. Example: 2026-10-01.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `to_date` (`string`, optional): End of the status change date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{"mailing_list_id":3456}`

### `activetrail_mailing_lists_list`

List Mailing Lists · Read-only

List the mailing lists of the ActiveTrail account.
Returns mailing lists with ID and name.
Use this to find mailing list IDs.

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

Inputs: none.

Example input: `{}`

### `activetrail_segmentations_list`

List Segmentations · Read-only

List the saved segmentations of the ActiveTrail account.
Returns segmentations with ID, name and rules.
Use this to find segments used by automations.

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

Inputs: none.

Example input: `{}`

### `activetrail_sending_profiles_list`

List Email Sending Profiles · Read-only

List the email sending profiles (from addresses) of the ActiveTrail account.
Returns profiles with ID, from name and from email.
Use this to get the user_profile_id needed to create campaigns and operational emails.

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

Inputs: none.

Example input: `{}`

### `activetrail_sent_campaigns_list`

List Sent Campaigns · Read-only

List the email campaigns the ActiveTrail account has sent.
Returns campaigns with ID, name, subject and send date.
Use this to find campaign IDs for reports.

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

Inputs: none.

Example input: `{}`

### `activetrail_signup_forms_list`

List Signup Forms · Read-only

List the signup forms of the ActiveTrail account.
Returns forms with ID, name and the groups they add contacts to.
Use this to see how contacts join.

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

Inputs: none.

Example input: `{}`

### `activetrail_sms_campaign_get`

Get SMS Campaign · Read-only

Get one ActiveTrail SMS campaign.
Returns the campaign's name, content, segment and scheduling.
Use this for an SMS campaign's details. Use activetrail_sms_campaign_report_get for its results.

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

Inputs:

- `sms_campaign_id` (`integer`, required): SMS campaign ID, from activetrail_sms_campaigns_list. Example: 55443.

Example input: `{"sms_campaign_id":55443}`

### `activetrail_sms_campaign_report_get`

Get SMS Campaign Report · Read-only

Get the summary report of one ActiveTrail SMS campaign.
Returns sent, delivered, failed, clicks and unsubscribes.
Use this for one SMS campaign's results.

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

Inputs:

- `sms_campaign_id` (`integer`, required): SMS campaign ID, from activetrail_sms_campaigns_list. Example: 55443.

Example input: `{"sms_campaign_id":55443}`

### `activetrail_sms_campaign_reports_list`

List SMS Campaign Reports · Read-only

List report summaries of ActiveTrail SMS campaigns.
Returns one row per campaign with sent, delivered, failed, clicks and unsubscribes.
Use this to compare SMS campaigns.

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

Inputs:

- `from_date` (`string`, optional): Start of the last update date range, YYYY-MM-DD. Example: 2026-10-01.
- `search_term` (`string`, optional): Campaign name or part of it. Example: Black Friday.
- `send_type` (`integer`, optional): Campaign type: 0 all, 1 regular, 2 operational, 3 automation. Example: 0.
- `to_date` (`string`, optional): End of the last update date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{}`

### `activetrail_sms_campaigns_list`

List SMS Campaigns · Read-only

List the SMS campaigns of the ActiveTrail account, including operational SMS.
Returns campaigns with ID, name, content, status and send date.
Use this to find SMS campaign IDs.

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

Inputs:

- `filter_type` (`integer`, optional): Campaign type: 0 all, 1 regular, 2 operational, 3 automation. Example: 0.
- `from_date` (`string`, optional): Start of the last update date range, YYYY-MM-DD. Example: 2026-10-01.
- `is_include_not_sent` (`boolean`, optional): True also lists campaigns not sent yet. Example: true.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `search_term` (`string`, optional): Campaign name or part of it. Example: Black Friday.
- `to_date` (`string`, optional): End of the last update date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{}`

### `activetrail_unsubscribers_list`

List Unsubscribers · Read-only

List contacts who unsubscribed, with the source of the unsubscription when known.
Returns unsubscribed contacts with email, date and source.
Use this to sync opt-outs to another system.

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

Inputs:

- `from_date` (`string`, optional): Start of the unsubscription date range, YYYY-MM-DD. Example: 2026-10-01.
- `limit` (`integer`, optional): Results per page, 1 to 100 (default 20). Example: 50.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `to_date` (`string`, optional): End of the unsubscription date range, YYYY-MM-DD. Example: 2026-10-31.

Example input: `{}`

### `activetrail_webhook_get`

Get Webhook · Read-only

Get one ActiveTrail webhook.
Returns the webhook's name, URL, event type, format and parameters.
Use this for a webhook's details.

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

Inputs:

- `webhook_id` (`integer`, required): Webhook ID, from activetrail_webhooks_list. Example: 321.

Example input: `{"webhook_id":321}`

### `activetrail_webhooks_list`

List Webhooks · Read-only

List the webhooks of the ActiveTrail account.
Returns webhooks with ID, name, URL, event type and state.
Use this to find webhook IDs.

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

Inputs:

- `event_type` (`integer`, optional): Only webhooks for this event type number, such as 8 contact added to group or 10 contact unsubscribed. Example: 10.
- `is_ignore_parameters` (`boolean`, optional): True leaves the webhook parameters out of the response. Example: true.

Example input: `{}`

### `activetrail_automation_activation_update`

Activate or Pause Automation · Write

Activate (publish) or pause an ActiveTrail automation, now or at a scheduled time.
Returns an empty success response.
Use this to turn an automation on or off.

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

Inputs:

- `automation_id` (`integer`, required): Automation ID, from activetrail_automations_list. Example: 7788.
- `is_published` (`boolean`, required): True activates the automation, false pauses it. Example: true.
- `scheduled_time` (`string`, optional): When to activate, ISO 8601; leave empty for now. Example: 2026-11-20T09:00:00.

Example input: `{"automation_id":7788,"is_published":true}`

### `activetrail_campaign_contacts_send`

Send Email Campaign to Contacts · Write

Create and send an ActiveTrail email campaign to specific contacts by email address or contact ID.
Returns the created campaign with its ID.
Use this for a small list of recipients. Use activetrail_campaign_create for groups.

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

Inputs:

- `content` (`string`, required): Email content as HTML or plain text. Example: Join us on December 1.
.
- `name` (`string`, required): Internal campaign name. Example: VIP invite.
- `subject` (`string`, required): Email subject line. Example: You're invited.
- `user_profile_id` (`integer`, required): Sending profile ID (the from address), from activetrail_sending_profiles_list. Example: 1122.
- `contacts_emails` (`array`, optional): Recipient email addresses. Required if contacts_ids is empty. Example: ["jane@example.com"]
- `contacts_ids` (`array`, optional): Recipient contact IDs. Required if contacts_emails is empty. Example: [123456]

Example input: `{"content":"<content>","name":"<name>","subject":"<subject>","user_profile_id":1122}`

### `activetrail_campaign_create`

Create Email Campaign · Write

Create an ActiveTrail email campaign to groups and schedule it, or send it now with is_sent true.
Returns the created campaign with its ID.
Use this to email groups. Use activetrail_campaign_contacts_send for specific contacts and activetrail_operational_email_send for transactional email.

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

Inputs:

- `content` (`string`, required): Email content as HTML or plain text. Example: <h1>Hello</h1>Here is our November update.
.
- `group_ids` (`array`, required): IDs of the groups to send to. Example: [45678]
- `is_sent` (`boolean`, required): True sends the campaign now; false schedules it for scheduled_date_utc. Example: false.
- `name` (`string`, required): Internal campaign name. Example: November newsletter.
- `scheduled_date_utc` (`string`, required): When to send, in UTC (ISO 8601). Use the current time with is_sent true. Example: 2026-11-20T09:00:00Z.
- `subject` (`string`, required): Email subject line. Example: What's new in November.
- `user_profile_id` (`integer`, required): Sending profile ID (the from address), from activetrail_sending_profiles_list. Example: 1122.
- `mailing_list_id` (`integer`, optional): Mailing list ID; required if the account uses mailing lists. Example: 3456.
- `preheader` (`string`, optional): Preheader text shown after the subject. Example: Our latest product updates.
- `send_test` (`string`, optional): Comma-separated email addresses to send a test copy to. Example: me@example.com.

Example input: `{"content":"<content>","group_ids":[45678],"is_sent":true,"name":"<name>","scheduled_date_utc":"<scheduled_date_utc>","subject":"<subject>","user_profile_id":1122}`

### `activetrail_contact_create`

Create Contact · Write

Create an ActiveTrail contact; it is not added to any group, so it cannot be mailed until you add it to one.
Returns the created contact with its ID.
Use activetrail_group_member_add instead to create a contact and put it in a group in one call.

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

Inputs:

- `birthday` (`string`, optional): Birthday, YYYY-MM-DD. Example: 1990-05-17.
- `city` (`string`, optional): City. Example: Tel Aviv.
- `email` (`string`, optional): Contact's email address. Required if sms is empty. Example: jane@example.com.
- `ext1` (`string`, optional): Custom field ext1; activetrail_contact_fields_list shows what each ext field holds. Example: Gold.
- `first_name` (`string`, optional): First name. Example: Jane.
- `last_name` (`string`, optional): Last name. Example: Doe.
- `phone1` (`string`, optional): Phone number. Example: +97231234567.
- `sms` (`string`, optional): Contact's mobile number. Required if email is empty. Example: +972501234567.
- `sms_status` (`integer`, optional): SMS subscription status as a number: 0 none, 1 subscribed, 2 unsubscribed, 3 pending. Example: 1. One of: `0`, `1`, `2`, `3`.
- `status` (`integer`, optional): Email subscription status as a number: 0 none, 1 subscribed, 2 unsubscribed, 3 pending. Example: 1. One of: `0`, `1`, `2`, `3`.
- `street` (`string`, optional): Street address. Example: 1 Rothschild Blvd.
- `subscribe_ip` (`string`, optional): IP address the contact subscribed from. Example: 203.0.113.10.
- `zip_code` (`string`, optional): Postal code. Example: 6688101.

Example input: `{}`

### `activetrail_contact_update`

Update Contact · Write

Update an ActiveTrail contact's details or subscription status.
Returns an empty success response.
Use this to change contact fields. Use activetrail_contact_get to read them.

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

Inputs:

- `contact_id` (`integer`, required): Contact ID, from activetrail_contacts_list. Example: 123456.
- `birthday` (`string`, optional): Birthday, YYYY-MM-DD. Example: 1990-05-17.
- `city` (`string`, optional): City. Example: Tel Aviv.
- `email` (`string`, optional): Contact's email address. Required if sms is empty. Example: jane@example.com.
- `ext1` (`string`, optional): Custom field ext1; activetrail_contact_fields_list shows what each ext field holds. Example: Gold.
- `first_name` (`string`, optional): First name. Example: Jane.
- `last_name` (`string`, optional): Last name. Example: Doe.
- `phone1` (`string`, optional): Phone number. Example: +97231234567.
- `sms` (`string`, optional): Contact's mobile number. Required if email is empty. Example: +972501234567.
- `sms_status` (`integer`, optional): SMS subscription status as a number: 0 none, 1 subscribed, 2 unsubscribed, 3 pending. Example: 1. One of: `0`, `1`, `2`, `3`.
- `status` (`integer`, optional): Email subscription status as a number: 0 none, 1 subscribed, 2 unsubscribed, 3 pending. Example: 1. One of: `0`, `1`, `2`, `3`.
- `street` (`string`, optional): Street address. Example: 1 Rothschild Blvd.
- `subscribe_ip` (`string`, optional): IP address the contact subscribed from. Example: 203.0.113.10.
- `zip_code` (`string`, optional): Postal code. Example: 6688101.

Example input: `{"contact_id":123456}`

### `activetrail_contacts_import`

Import Contacts · Write

Import up to 1,000 contacts into an ActiveTrail group, creating or updating them.
Returns the import result with counts of created, updated and failed contacts.
Use this for bulk adds. Use activetrail_group_member_add for one contact.

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

Inputs:

- `contacts` (`array`, required): Contacts to import, each an object with Email or SMS and optional FirstName, LastName, City, Phone1, Birthday and Ext1..Ext25. Example: [{"Email": "jane@example.com", "FirstName": "Jane"}, {"SMS": "+972501234567"}]
- `group` (`integer`, required): ID of the group to import into. Example: 45678.
- `mailing_list` (`integer`, optional): ID of a mailing list to add the contacts to; leave empty if the account has no mailing lists. Example: 3456.

Example input: `{"contacts":[{"Email":"jane@example.com","FirstName":"Jane"},{"SMS":"+972501234567"}],"group":45678}`

### `activetrail_group_create`

Create Group · Write

Create an ActiveTrail contact group.
Returns the created group with its ID.
Use this to add a group. Use activetrail_group_member_add to fill it.

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

Inputs:

- `name` (`string`, required): Group name. Example: Newsletter subscribers.

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

### `activetrail_group_member_add`

Add Group Member · Write

Add a contact to an ActiveTrail group, creating the contact if needed, and set its status; optionally send it a campaign.
Returns the contact as added.
Use this to subscribe someone to a group. Contacts that are inactive cannot be re-added as subscribed.

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

Inputs:

- `group_id` (`integer`, required): Group ID, from activetrail_groups_list or the group's URL in ActiveTrail (Contacts > Groups). Example: 45678.
- `birthday` (`string`, optional): Birthday, YYYY-MM-DD. Example: 1990-05-17.
- `campaign_id` (`integer`, optional): ID of a campaign to send to the added contact. Example: 987654.
- `city` (`string`, optional): City. Example: Tel Aviv.
- `email` (`string`, optional): Contact's email address. Required if sms is empty. Example: jane@example.com.
- `ext1` (`string`, optional): Custom field ext1; activetrail_contact_fields_list shows what each ext field holds. Example: Gold.
- `first_name` (`string`, optional): First name. Example: Jane.
- `last_name` (`string`, optional): Last name. Example: Doe.
- `phone1` (`string`, optional): Phone number. Example: +97231234567.
- `sms` (`string`, optional): Contact's mobile number. Required if email is empty. Example: +972501234567.
- `sms_status` (`integer`, optional): SMS subscription status as a number: 0 none, 1 subscribed, 2 unsubscribed, 3 pending. Example: 1. One of: `0`, `1`, `2`, `3`.
- `status` (`integer`, optional): Email subscription status as a number: 0 none, 1 subscribed, 2 unsubscribed, 3 pending. Example: 1. One of: `0`, `1`, `2`, `3`.
- `street` (`string`, optional): Street address. Example: 1 Rothschild Blvd.
- `subscribe_ip` (`string`, optional): IP address the contact subscribed from. Example: 203.0.113.10.
- `zip_code` (`string`, optional): Postal code. Example: 6688101.

Example input: `{"group_id":45678}`

### `activetrail_group_update`

Rename Group · Write

Rename an ActiveTrail group.
Returns an empty success response.
Use this to change a group's name.

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

Inputs:

- `group_id` (`integer`, required): Group ID, from activetrail_groups_list or the group's URL in ActiveTrail (Contacts > Groups). Example: 45678.
- `name` (`string`, required): New group name. Example: Newsletter 2026.

Example input: `{"group_id":45678,"name":"<name>"}`

### `activetrail_mailing_list_create`

Create Mailing List · Write

Create an ActiveTrail mailing list.
Returns the created mailing list with its ID.
Use this to add a mailing list.

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

Inputs:

- `name` (`string`, required): Mailing list name. Example: Customers.

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

### `activetrail_mailing_list_member_add`

Add Mailing List Member · Write

Add a contact to an ActiveTrail mailing list and to one or more groups.
Returns the contact as added.
Use this for accounts that use mailing lists.

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

Inputs:

- `group_ids` (`array`, required): IDs of the groups to add the contact to. Example: [45678]
- `mailing_list_id` (`integer`, required): Mailing list ID, from activetrail_mailing_lists_list. Example: 3456.
- `email` (`string`, optional): Contact's email address. Required if sms is empty. Example: jane@example.com.
- `first_name` (`string`, optional): First name. Example: Jane.
- `last_name` (`string`, optional): Last name. Example: Doe.
- `sms` (`string`, optional): Contact's mobile number. Required if email is empty. Example: +972501234567.
- `sms_status` (`integer`, optional): SMS subscription status as a number: 0 none, 1 subscribed, 2 unsubscribed, 3 pending. Example: 1. One of: `0`, `1`, `2`, `3`.
- `status` (`integer`, optional): Email subscription status as a number: 0 none, 1 subscribed, 2 unsubscribed, 3 pending. Example: 1. One of: `0`, `1`, `2`, `3`.

Example input: `{"group_ids":[45678],"mailing_list_id":3456}`

### `activetrail_operational_email_send`

Send Operational Email · Write

Send a transactional (operational) email to up to 500 addresses, with per-recipient personalization; recipients are created as contacts.
Returns the sent message details.
Use this for receipts and notifications. Use activetrail_campaign_create for marketing email.

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

Inputs:

- `classification` (`string`, required): Category for grouping operational messages in reports, such as Order shipped. Example: Order shipped.
- `content` (`string`, required): Email content as HTML; personalization keys from email_package pairs can be used. Example: Hi, your order has shipped.
.
- `email_package` (`array`, required): Recipients, each an object with email and optional pairs of key/value personalization. Example: [{"email": "jane@example.com", "pairs": [{"key": "order", "value": "1001"}]}]
- `subject` (`string`, required): Email subject. Example: Your order #1001 has shipped.
- `user_profile_id` (`integer`, required): Sending profile ID (the from address), from activetrail_sending_profiles_list. Example: 1122.
- `name` (`string`, optional): Internal name of the message. Example: Shipping confirmation.

Example input: `{"classification":"<classification>","content":"<content>","email_package":[],"subject":"<subject>","user_profile_id":1122}`

### `activetrail_operational_sms_send`

Send Operational SMS · Write

Send a transactional (operational) SMS to specific mobile numbers, now or scheduled.
Returns the created operational SMS.
Use this for one-to-one texts such as codes and alerts. Use activetrail_sms_campaign_create for groups.

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

Inputs:

- `content` (`string`, required): SMS text. Example: Your order arrives today between 10:00 and 12:00.
- `mobiles` (`array`, required): Recipients, each an object with phone_number. Example: [{"phone_number": "+972501234567"}]
- `name` (`string`, required): Internal name of the message. Example: Delivery alert.
- `send_now` (`boolean`, required): True sends now; false sends at scheduled_date_utc. Example: true.
- `from_name` (`string`, optional): Sender name. Required if sms_sending_profile_id is empty. Example: AcmeShop.
- `scheduled_date_utc` (`string`, optional): When to send, in UTC (ISO 8601), if not sending now. Example: 2026-11-20T09:00:00Z.
- `sms_sending_profile_id` (`integer`, optional): SMS sending profile ID. Required if from_name is empty. Example: 77.

Example input: `{"content":"<content>","mobiles":[{"phone_number":"+972501234567"}],"name":"<name>","send_now":true}`

### `activetrail_sms_campaign_create`

Create SMS Campaign · Write

Create an ActiveTrail SMS campaign to groups and send it now or schedule it.
Returns the created SMS campaign with its ID.
Use this to text groups. Use activetrail_operational_sms_send for specific numbers.

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

Inputs:

- `content` (`string`, required): SMS text. Example: Black Friday: 30% off everything today only!.
- `group_ids` (`array`, required): IDs of the groups to send to. Example: [45678]
- `is_sent` (`boolean`, required): True sends the campaign now; false sends at scheduled_date. Example: true.
- `name` (`string`, required): Internal campaign name. Example: Black Friday SMS.
- `unsubscribe_text` (`string`, required): Unsubscribe text, required even when no unsubscribe link is added. Example: Reply STOP to unsubscribe.
- `can_unsubscribe` (`boolean`, optional): True adds an unsubscribe link. Example: true.
- `from_name` (`string`, optional): Sender name, up to 11 characters. Required if sms_sending_profile_id is empty. Example: AcmeShop.
- `is_link_tracking` (`boolean`, optional): True tracks links in the SMS. Example: true.
- `scheduled_date` (`string`, optional): When to send, ISO 8601, if not sending now. Example: 2026-11-27T08:00:00.
- `sms_sending_profile_id` (`integer`, optional): SMS sending profile ID. Required if from_name is empty. Example: 77.

Example input: `{"content":"<content>","group_ids":[45678],"is_sent":true,"name":"<name>","unsubscribe_text":"<unsubscribe_text>"}`

### `activetrail_webhook_create`

Create Webhook · Write

Create an ActiveTrail webhook that calls your URL when an event happens, such as a contact unsubscribing.
Returns the created webhook with its ID.
Use this to get event notifications.

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

Inputs:

- `event_type` (`integer`, required): Event number: 1 contact change, 6 manual contact change, 7 automation step, 8 added to group, 9 removed from group, 10 unsubscribed, 11 contact updated, 12 added via landing page, 13 added via signup form, 14 order created, 15 order updated, 16 lead created, 17 lead updated, 18 opportunity created, 19 opportunity updated. Example: 10.
- `name` (`string`, required): Webhook name. Example: Unsubscribe sync.
- `url` (`string`, required): URL ActiveTrail calls. Example: https://example.com/hooks/activetrail.
- `format` (`integer`, optional): Payload format: 1 JSON, 2 form URL-encoded. Example: 1. One of: `1`, `2`.
- `is_active` (`boolean`, optional): True turns the webhook on. Example: true.

Example input: `{"event_type":10,"name":"<name>","url":"<url>"}`

### `activetrail_campaign_delete`

Delete Email Campaign · Destructive

Delete an ActiveTrail email campaign.
Returns an empty success response.
Use this to remove a draft or scheduled campaign.

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

Inputs:

- `campaign_id` (`integer`, required): Email campaign ID, from activetrail_sent_campaigns_list or activetrail_campaign_reports_list. Example: 987654.

Example input: `{"campaign_id":987654}`

### `activetrail_contact_delete`

Delete Contact · Destructive

Delete an ActiveTrail contact.
Returns an empty success response.
Use this to remove a contact for good. Use activetrail_contact_update with status 2 to unsubscribe instead.

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

Inputs:

- `contact_id` (`integer`, required): Contact ID, from activetrail_contacts_list. Example: 123456.

Example input: `{"contact_id":123456}`

### `activetrail_group_delete`

Delete Group · Destructive

Delete an ActiveTrail group; its contacts stay in the account.
Returns an empty success response.
Use this to remove a group.

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

Inputs:

- `group_id` (`integer`, required): Group ID, from activetrail_groups_list or the group's URL in ActiveTrail (Contacts > Groups). Example: 45678.

Example input: `{"group_id":45678}`

### `activetrail_group_member_remove`

Remove Group Member · Destructive

Remove a contact from an ActiveTrail group; the contact stays in the account.
Returns an empty success response.
Use this to take someone out of a group.

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

Inputs:

- `contact_id` (`integer`, required): ID of the contact to remove, from activetrail_group_members_list. Example: 123456.
- `group_id` (`integer`, required): Group ID, from activetrail_groups_list or the group's URL in ActiveTrail (Contacts > Groups). Example: 45678.

Example input: `{"contact_id":123456,"group_id":45678}`

### `activetrail_mailing_list_delete`

Delete Mailing List · Destructive

Delete an ActiveTrail mailing list.
Returns an empty success response.
Use this to remove a mailing list.

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

Inputs:

- `mailing_list_id` (`integer`, required): Mailing list ID, from activetrail_mailing_lists_list. Example: 3456.

Example input: `{"mailing_list_id":3456}`

### `activetrail_mailing_list_member_remove`

Remove Mailing List Member · Destructive

Remove a contact from an ActiveTrail mailing list.
Returns an empty success response.
Use this to take someone off a mailing list.

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

Inputs:

- `contact_id` (`integer`, required): ID of the contact to remove. Example: 123456.
- `mailing_list_id` (`integer`, required): Mailing list ID, from activetrail_mailing_lists_list. Example: 3456.

Example input: `{"contact_id":123456,"mailing_list_id":3456}`

### `activetrail_webhook_delete`

Delete Webhook · Destructive

Delete an ActiveTrail webhook.
Returns an empty success response.
Use this to stop event notifications.

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

Inputs:

- `webhook_id` (`integer`, required): Webhook ID, from activetrail_webhooks_list. Example: 321.

Example input: `{"webhook_id":321}`

## 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 |
