/acelle-mail

name: acelle-mail
description: |
  Acelle Mail integration. Manage Users. Use when the user wants to interact with Acelle Mail 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: ""

Acelle Mail

Acelle Mail is a self-hosted email marketing application, similar to MailChimp, allowing users to send bulk emails. It's used by businesses and individuals who want to manage their own email marketing campaigns without relying on third-party services.

Official docs: https://acellemail.com/docs/

Acelle Mail Overview

• **Email Marketing Server**
• **Customer**
• **Subscription**
• **Sending Server**
• **Email Verification Server**
• **Blacklist**
• **Campaign**
• **Template**
• **Mail List**
• **Subscriber**
• **Automation**
• **Segment**

Use action names and parameters as needed.

Working with Acelle Mail

This skill uses the Membrane CLI to interact with Acelle Mail. 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 Acelle Mail

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

membrane connection ensure "https://acellemail.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 Campaigns | list-campaigns | Retrieve all campaigns with their details | | List Subscribers | list-subscribers | Retrieve subscribers from a mail list with pagination | | List Lists | list-lists | Retrieve all mail lists with their details including name, description, and unique UID | | Get Campaign | get-campaign | Get detailed information about a specific campaign including statistics | | Get Subscriber | get-subscriber | Get detailed information about a specific subscriber by UID | | Get List | get-list | Get detailed information about a specific mail list by its UID | | Create Campaign | create-campaign | Create a new email campaign | | Create List | create-list | Create a new mail list for organizing contacts | | Add Subscriber | add-subscriber | Add a new subscriber to a mail list | | Update Campaign | update-campaign | Update an existing campaign | | Update Subscriber | update-subscriber | Update subscriber information | | Delete Subscriber | delete-subscriber | Permanently delete a subscriber from the system | | Delete List | delete-list | Delete a mail list by its UID | | Run Campaign | run-campaign | Launch a campaign to start sending emails | | Pause Campaign | pause-campaign | Pause a running campaign | | Resume Campaign | resume-campaign | Resume a paused campaign | | Subscribe | subscribe | Subscribe or reactivate a subscriber in a mail list | | Unsubscribe | unsubscribe | Unsubscribe a subs