/airslate

name: airslate
description: |
  Airslate integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airslate 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: ""

Airslate

AirSlate is a document workflow automation platform. It's used by businesses of all sizes to streamline and automate document creation, e-signature, and routing processes. Think of it as a no-code solution for automating paperwork.

Official docs: https://developers.airslate.com/

Airslate Overview

• **Slate**
• **Template**
• **Bot**
• **Flow**
• **User**
• **Organization**
• **Integration**

Working with Airslate

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

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

membrane connection ensure "https://www.airslate.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 Organizations | list-organizations | Retrieve a list of all organizations that the current user belongs to | | List Templates | list-templates | Retrieve a list of templates available in a specific organization | | List Workflows | list-workflows | Retrieve a list of workflows in a specific template | | List Organization Users | list-organization-users | Retrieve information about all users in an organization | | List Webhooks | list-webhooks | Access all webhooks created by the current user in an organization | | List Web Forms | list-web-forms | Get a list of form templates in an organization | | Get Template | get-template | Get detailed information about a template by its ID | | Get Workflow | get-workflow | Retrieve information about a specific workflow by its ID | | Get Webhook | get-webhook | Get information about a specific webhook | | Get Organization User | get-organization-user | Get user data in an organization | | Create Organization | create-organization | Create a new organization | | Create Template | create-template | Create a new template in the specified organization | | Create Workflow | create-workflow | Run a workflow from a specific template to generate documents and send them for signature | | Create Webhook | create-webhook | Create a new webhook to subscribe to an event | | Update Template | update-template | Update a template in the specified organization | | Update Organization User | update-organization-user | Update user data in an organization | | Delete Template | delete-template | Delete a specific template (only unpublished templates can be deleted) | | Delete Webhook | delete-we