Front integration. Manage Conversations, Contacts, Tags, Channels, Teams, Users. Use when the user wants to interact with Front data.
Front is a customer communication hub that combines email, messaging, and apps into one platform. Customer support, sales, and account management teams use it to manage all their conversations in one place and collaborate more effectively.
Official docs: https://developers.frontapp.com/
Use action names and parameters as needed.
This skill uses the Membrane CLI to interact with Front. 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/cli
membrane login --tenant
A 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 front --elementType=connector --json
Take the connector ID from output.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --json
The user completes authentication in the browser. The output contains the new connection id.When you are not sure if connection already exists:
membrane connection list --json
If a Front connection exists, note its connectionIdWhen you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
This will return action objects with id and inputSchema in it, so you will know how to run it.
| Name | Key | Description |
|---|---|---|
| List Conversations | list-conversations | List all conversations in Front with optional pagination |
| List Contacts | list-contacts | List all contacts in Front with optional pagination |
| List Inboxes | list-inboxes | List all inboxes in Front |
| List Teammates | list-teammates | List all teammates in Front |
| List Teams | list-teams | List all teams in the organization |
| List Tags | list-tags | List all tags in Front |
| List Channels | list-channels | List all channels in Front |
| List Message Templates | list-message-templates | List all message templates (canned responses) |
| List Rules | list-rules | List all automation rules in the company |
| Get Conversation | get-conversation | Retrieve a specific conversation by ID |
| Get Contact | get-contact | Retrieve a specific contact by ID |
| Get Inbox | get-inbox | Retrieve a specific inbox by ID |
| Get Teammate | get-teammate | Retrieve a specific teammate by ID |
| Get Team | get-team | Get a specific team by ID |
| Get Tag | get-tag | Retrieve a specific tag by ID |
| Create Contact | create-contact | Create a new contact in Front |
| Create Tag | create-tag | Create a new tag in Front |
| Update Conversation | update-conversation | Update a conversation's properties (assignee, status, tags, etc.) |
| Update Contact | update-contact | Update an existing contact in Front |
| Delete Contact | delete-contact | Delete a contact from Front |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
To 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 Front 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/endpoint
Common 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.ZIP package — ready to use