/active-trail

name: active-trail
description: |
  Active Trail integration. Manage data, records, and automate workflows. Use when the user wants to interact with Active Trail data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""

Active Trail

Active Trail is an email marketing automation platform. It allows businesses to create and manage email campaigns, track results, and automate marketing processes. It's used by marketing teams and small business owners to engage with customers and grow their business.

Official docs: https://support.activetrail.com/hc/en-us

Active Trail Overview

• **Contacts**
• **Contact Lists**
• **Campaigns**
• **Automations**
• **Reports**
• **Landing Pages**
• **SMS**
• **Email Marketing**
• **CRM**
• **Integrations**
• **Settings**

Working with Active Trail

This skill uses the Membrane CLI to interact with Active Trail. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to Active Trail

Use `membrane connection ensure` to find or create a connection by app URL or domain:

membrane connection ensure "https://activetrail.com/" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

• **`READY`** — connection is fully set up. Skip to **Step 2**.
• **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
• `clientAction.type` — the kind of action needed:
• `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
• `"provide-input"` — more information is needed (e.g. which app to connect to).
• `clientAction.description` — human-readable explanation of what's needed.
• `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
• `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

• **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

Popular actions

| Name | Key | Description | |---|---|---| | List Contacts | list-contacts | Get a list of contacts from your Active Trail account with optional filtering | | List Mailing Lists | list-mailing-lists | Get all mailing lists | | List Campaigns | list-campaigns | Get all email campaigns | | List Groups | list-groups | Get all groups from your Active Trail account | | List Automations | list-automations | Get all automations in the account | | List Templates | list-templates | Get all email templates | | Get Contact | get-contact | Get a single contact by ID | | Get Mailing List | get-mailing-list | Get a single mailing list by ID | | Get Campaign | get-campaign | Get a single campaign by ID | | Get Group | get-group | Get a single group by ID | | Get Automation | get-automation | Get a single automation by ID | | Get Template | get-template | Get a single template by ID | | Create Contact | create-contact | Create a new contact in your Active Trail account | | Create Mailing List | create-mailing-list | Create a new mailing list | | Create Group | create-group | Create a new contact group | | Update Contact | update-contact | Update an existing contact | | Update Group | update-group | Update an existing group | | Delete Contact | delete-contact | Delete a contact by ID | | Delete Mailing List | delete-mailing-list | Delete a mailing list by ID | | Delete Group | delete-group | Delete a group by ID |

Running actions

membrane action run <actionId> --connectionId=CONNECTION_ID --json

To pass