/amcards

name: amcards
description: |
  AMcards integration. Manage Cards, Users, Templates, Contacts, Groups. Use when the user wants to interact with AMcards 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: ""

AMcards

AMcards is a digital business card platform. Professionals and businesses use it to create, share, and manage their digital business cards. It helps users network and exchange contact information more efficiently.

Official docs: https://amcards.com/developer-api/

AMcards Overview

• **Card**
• **Card Content**
• **Deck**
• **User**

Working with AMcards

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

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

membrane connection ensure "https://amcards.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 Quicksend Templates | list-quicksend-templates | Retrieve a list of quicksend templates available in your AMcards account | | Get Quicksend Template | get-quicksend-template | Retrieve a specific quicksend template by its ID | | List Credit Transactions | list-credit-transactions | Retrieve a list of credit transactions from your AMcards account | | Get Mailing | get-mailing | Retrieve a specific mailing (batch of campaign cards) by its ID | | Send Campaign | send-campaign | Send a drip campaign to a recipient. | | Send Card | send-card | Send a card to a recipient using a template. | | Delete Contact | delete-contact | Delete a contact from your AMcards account | | Create Contact | create-contact | Create a new contact in your AMcards account | | Get Contact | get-contact | Retrieve a specific contact by its ID | | List Contacts | list-contacts | Retrieve a list of contacts stored in your AMcards account | | Get Card | get-card | Retrieve a specific card by its ID | | List Cards | list-cards | Retrieve a list of cards that have been sent from your AMcards account | | Get Campaign | get-campaign | Retrieve a specific drip campaign by its ID | | List Campaigns | list-campaigns | Retrieve a list of drip campaigns available in your AMcards account | | Get Template | get-template | Retrieve a specific card template by its ID | | List Templates | list-templates | Retrieve a list of card templates available in your AMcards account | | Get Current User | get-current-user | Retrieve the current authenticated AMcards user's profile information including credits, address, and postage costs |

Running actions

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