Active Trail integration. Manage data, records, and automate workflows. Use when the user wants to interact with Active Trail data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill active-trail72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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
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 Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/climembrane login --tenantA browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
membrane search active-trail --elementType=connector --jsonoutput.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --jsonWhen you are not sure if connection already exists:
membrane connection list --jsonconnectionIdWhen you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --jsonThis will return action objects with id and inputSchema in it, so you will know how to run it.
| 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 |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --jsonTo pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"When the available actions don't cover your use case, you can send requests directly to the Active Trail API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpointCommon options:
| Flag | Description |
|---|---|
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data | Request body (string) |
--json | Shorthand to send a JSON body and set Content-Type: application/json |
--rawData | Send the body as-is without any processing |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.d19a82b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.