Mattering Automations connector
The Front MCP for support teams that automate the busywork
Connect Front once and your conversations, contacts, tags, and inboxes become building blocks for visual automations and AI agent workflows. 91 nodes covering the Front core API.
What the Front MCP connector does
The Front connector for Mattering Automations covers the Front core API in depth: list, assign, and tag conversations, send replies and new channel messages, draft for human review, comment internally, and manage contacts, accounts, tags, inboxes, teammates, links, and events.
Each capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any MCP-capable assistant can use them, and they also power Matter, the platform's AI assistant. Describe the triage flow you want in plain language and it gets built on the canvas in front of you.
An advanced custom request node can call any Front core API path, so even endpoints beyond the 91 typed nodes stay reachable without waiting on a connector update.
One connection, three surfaces
- Visual automations. Drag Front nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Front node, ready to drop on the canvas
91 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 44
Front: Download Attachment
Download an attachment by its link ID (returns file bytes; non-JSON responses surface as raw_body).
Front: Get API Token Details
Get the company identity tied to the API token.
Front: Get Account
Get a single account.
Front: Get Channel
Get a single channel.
Front: Get Comment
Get a single comment.
Front: Get Contact
Get a single contact (contact_id accepts an alt:<source>:<handle> alias).
Front: Get Conversation
Get a single conversation.
Front: Get Event
Get a single event.
Front: Get Inbox
Get a single inbox.
Front: Get Link
Get a single link.
Front: Get Message
Get a single message (headers, body, recipients, attachments).
Front: Get Message Seen Status
Get the seen receipts of a message.
Front: Get Tag
Get a single tag.
Front: Get Team
Get a single team with its inboxes and members.
Front: Get Teammate
Get a single teammate (teammate_id accepts an email alias).
Front: List Account Contacts
List the contacts associated with an account.
Front: List Accounts
List the accounts (companies) in the company.
Front: List Channels
List the channels in the company.
Front: List Comment Mentions
List the teammates mentioned in a comment.
Front: List Contact Conversations
List the conversations involving a contact.
Front: List Contact Notes
List the notes on a contact.
Front: List Contacts
List contacts in the company (filterable, paginated).
Front: List Conversation Comments
List the comments in a conversation.
Front: List Conversation Drafts
List the drafts in a conversation.
Front: List Conversation Events
List the activity events of a conversation.
Front: List Conversation Followers
List the teammates following a conversation.
Front: List Conversation Inboxes
List the inboxes a conversation appears in.
Front: List Conversation Messages
List the messages in a conversation.
Front: List Conversations
List conversations in the company (filterable with q, paginated).
Front: List Events
List activity events company-wide (filter with q: before/after/types/inboxes).
Front: List Inbox Channels
List the channels attached to an inbox.
Front: List Inbox Conversations
List the conversations in an inbox (filterable, paginated).
Front: List Inbox Teammates
List the teammates with access to an inbox.
Front: List Inboxes
List the inboxes in the company.
Front: List Link Conversations
List the conversations attached to a link.
Front: List Links
List the links in the company.
Front: List Tag Children
List the children of a tag.
Front: List Tagged Conversations
List the conversations tagged with a tag.
Front: List Tags
List the tags visible to the token.
Front: List Teammate Conversations
List the conversations assigned to a teammate.
Front: List Teammate Inboxes
List the inboxes a teammate can access.
Front: List Teammates
List the teammates in the company.
Front: List Teams
List the teams (workspaces) in the company.
Front: Search Conversations
Full-text conversation search using Front's search query syntax.
Action nodes 47
Front: Add Comment
Add an internal comment to a conversation (body: {body, author_id, ...}).
Front: Add Contact Handle
Add a handle (email, phone, ...) to a contact (body: {handle, source}).
Front: Add Contact Note
Add a note to a contact (body: {author_id, body}).
Front: Add Contacts to Account
Associate contacts with an account (body: {contact_ids}).
Front: Add Conversation Followers
Add teammates as followers of a conversation (body: {teammate_ids}).
Front: Add Conversation Links
Add links to a conversation (body: {link_ids} or {link_external_urls}).
Front: Add Conversation Tags
Add one or more tags to a conversation (body: {tag_ids: [...]}).
Front: Add Inbox Access
Give teammates access to an inbox (body: {teammate_ids}).
Front: Assign Conversation
Assign or unassign a conversation (body: {assignee_id}).
Front: Create Account
Create an account (body: {name, domains, custom_fields, ...}).
Front: Create Child Tag
Create a child tag under a parent tag.
Front: Create Company Tag
Create a company-level tag (body: {name, highlight?, ...}).
Front: Create Contact
Create a contact (body: {name, handles, links, custom_fields, ...}).
Front: Create Discussion Conversation
Create a discussion or task conversation (comment-only types).
Front: Create Draft
Create a new-message draft in a channel (creates its conversation).
Front: Create Draft Reply
Create a reply draft in an existing conversation.
Front: Create Inbox
Create an inbox in the default team (body: {name, teammate_ids}).
Front: Create Link
Create a link (body: {name?, external_url}).
Front: Create Tag (legacy)
Create a tag in the oldest team workspace (legacy — prefer Create Company Tag).
Front: Delete Account
Delete an account.
Front: Delete Contact
Delete a contact.
Front: Delete Contact Handle
Remove a handle from a contact (body: {handle, source}).
Front: Delete Draft
Delete a draft (requires the draft's current version in the body).
Front: Delete Tag
Delete a tag.
Front: Edit Draft
Edit a draft (requires the draft's current version in the body).
Front: Import Message
Import a historical message into an inbox without triggering rules or notifications.
Front: Mark Message Seen
Mark an outbound message as seen (for channels with read receipts).
Front: Merge Contacts
Merge contacts into one (body: {contact_ids, target_contact_id?}).
Front: Receive Custom Message
Push an inbound message into a custom channel (body: {sender, subject, body, ...}).
Front: Remove Contacts from Account
Remove contacts from an account (body: {contact_ids}).
Front: Remove Conversation Followers
Remove teammate followers from a conversation (body: {teammate_ids}).
Front: Remove Conversation Links
Remove links from a conversation (body: {link_ids: [...]}).
Front: Remove Conversation Tags
Remove one or more tags from a conversation (body: {tag_ids: [...]}).
Front: Remove Inbox Access
Revoke teammates' access to an inbox (body: {teammate_ids}).
Front: Reply to Comment
Reply to a comment thread.
Front: Reply to Conversation
Send a reply in an existing conversation (body: {body, to, channel_id, ...}).
Front: Send New Message
Send a new message from a channel, creating a new conversation (body: {to, subject, body, ...}). channel_id accepts a channel address alias.
Front: Update Account
Update an account.
Front: Update Channel
Update a channel's settings.
Front: Update Comment
Edit a comment's body.
Front: Update Contact
Update a contact.
Front: Update Conversation
Update a conversation (status, assignee, inbox, tags, custom fields).
Front: Update Conversation Reminders
Snooze or unsnooze a conversation for a teammate.
Front: Update Link
Update a link's name.
Front: Update Tag
Update a tag (name, highlight, parent).
Front: Update Teammate
Update a teammate (username, name, availability).
Front: Validate Channel
Ask Front to re-validate a channel's connection.
Connecting Front takes one credential
Front connects with an API token. Create one in Front under Settings, then Developers, then API tokens, choosing the scopes the token should carry.
In Front, create an API token with the scopes your automations need.
In Mattering Automations, open Connectors, choose Front, and attach a secret holding the token.
The connector verifies the token against Front's identity endpoint.
All Front nodes appear in the canvas palette, ready to use.
Common uses for the Front MCP
Auto-triage inbound conversations
Tag, assign, and route new conversations by rule or by agent judgment, so the right teammate sees the right thread without a human dispatcher.
AI-drafted replies with human review
An agent reads the conversation and creates a draft reply in Front. Your team reviews and sends, keeping a person in the loop on every outbound message.
Conversations that become tasks
When a thread is tagged as a bug or a request, create a task in Mattering Productivity with the conversation link, assignee, and due date filled in.
Internal comments for context
Post internal comments summarizing long threads, flagging churn risk, or handing off between shifts, without touching the customer-facing conversation.
Contact and account hygiene
Create and update contacts and accounts as conversations arrive, merge duplicates, and append notes so the customer record stays current.
Escalation workflows
Watch for keywords or tags, then assign to a senior inbox, notify the owner, and set a follow-up reminder in one flow.
Example: Urgent conversations become tracked work
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a scheduled check lists Front conversations tagged urgent.
Front: Get Conversation pulls the thread details and assignee.
Mattering Productivity: a task is created with the conversation summary and a link back to Front.
Front: Create Comment posts an internal note confirming the task id, so the support team knows it is tracked.
Front MCP questions, answered
Can an AI agent reply to Front conversations through this MCP?
Yes. Matter and any MCP-connected assistant, including Claude and ChatGPT, can send replies and new channel messages directly, or create drafts for a teammate to review and send. For customer-facing email, the draft nodes keep a human in the loop.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with Front through them. Matter, the assistant built into the platform, uses the same nodes natively.
Which parts of Front does the connector cover?
91 typed nodes across conversations, messages, comments, drafts, inboxes, channels, contacts, tags, teammates, teams, links, accounts, events, and attachment downloads, plus a custom request node for any other Front core API path.
What credential does it use?
A Front API token, sent as a bearer credential and stored encrypted in Google Secret Manager. Scopes are set when you create the token in Front, so you control what automations can touch.
Can it create conversations from scratch?
Yes, by sending a new message through one of your Front channels, which starts a conversation. Importing historical messages is also supported through the import node.
Does it support Front analytics or the partner channel API?
Those endpoints are not among the typed nodes, but the custom request node can call any Front core API path your token is scoped for. Partner-only surfaces require partner credentials from Front.
What are Front's API rate limits?
Front enforces rate limits per company based on plan, and its developer documentation is the source of truth for current numbers. The connector surfaces rate limit errors on the node output so workflows can retry.
How is this different from Zapier's Front integration?
Mattering combines Front with native tasks, projects, and AI agents in one platform. A conversation can become a tracked task, an agent can draft the reply, and the whole flow lives on one canvas you can see and edit.
Put Front to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Front is a product of its respective owner; Mattering is an independent platform.