Aimtell integration. Manage data, records, and automate workflows. Use when the user wants to interact with Aimtell data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill aimtell61
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
Aimtell is a web push notification platform that allows businesses to send targeted messages to their website visitors. It's used by marketers and website owners to re-engage users, drive conversions, and increase website traffic. Think of it as a way to send notifications directly to a user's desktop or mobile device, even when they're not on your website.
Official docs: https://docs.aimtell.com/
This skill uses the Membrane CLI to interact with Aimtell. 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 aimtell --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 Campaigns | list-campaigns | No description |
| List Segments | list-segments | No description |
| List Subscribers | list-subscribers | No description |
| List Websites | list-websites | No description |
| List Event Triggered Campaigns | list-event-triggered-campaigns | No description |
| List Opt-in Prompts | list-opt-in-prompts | No description |
| Get Campaign | get-campaign | No description |
| Get Segment | get-segment | No description |
| Get Subscriber | get-subscriber | No description |
| Get Website | get-website | No description |
| Get Welcome Campaign | get-welcome-campaign | No description |
| Get Event Triggered Campaign | get-event-triggered-campaign | No description |
| Get Website Settings | get-website-settings | No description |
| Create Campaign | create-campaign | No description |
| Create Segment | create-segment | No description |
| Create Website | create-website | No description |
| Update Campaign | update-campaign | No description |
| Update Segment | update-segment | No description |
| Update Website Settings | update-website-settings | No description |
| Delete Campaign | delete-campaign | No description |
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 Aimtell 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.