Integration

Front integration

Customer communication platform API for managing shared inboxes, conversations, and team collaboration. Handle emails, SMS, social messages in one place. Assign conversations, add comments, apply tags, and automate workflows. Essential for customer support, sales teams, and operations.

Connect Front How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Front.Built from the 20 Front tools below, on the connection you add once.

Common Front use cases

CRM sync
ticket assignment
conversation display
categorization
team management
channel discovery
conversation routing
outreach
tag selection
contact update

What you can do with Front

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Conversation, 6 operations

create_conversationCreate conversationPOSTCreates a new outbound conversation by sending a message through a channel.
get_conversationGet conversationGETRetrieves a specific conversation with full details including assignee, tags, and status.
list_conversationsList conversationsGETLists conversations with search filtering and pagination. Returns conversation metadata and status.
search_conversationsSearch conversationsGETSearches conversations using Front's search syntax with text and filter support.
update_conversationUpdate conversationPATCHUpdates a conversation's assignee, status, inbox, tags, or custom fields.
update_conversation_assigneeUpdate conversation assigneePUTAssigns or unassigns a conversation to a specific teammate.

Contact, 4 operations

create_contactCreate contactPOSTCreates a new contact with one or more handles (email, phone, etc.).
get_contactGet contactGETRetrieves a contact's profile and handles by ID or by resource alias (email, phone).
list_contactsList contactsGETLists all contacts in the company with optional filtering and sorting.
update_contactUpdate contactPATCHUpdates a contact's name, description, links, lists, or custom fields.

Message, 3 operations

get_messageGet messageGETRetrieves a specific message with full details including body, sender, recipients, and attachments.
list_conversation_messagesList conversation messagesGETLists all messages within a conversation including sender info, timestamps, and content.
send_replySend replyPOSTSends a reply message within a conversation to the customer or contact.

Tag, 2 operations

add_conversation_tagAdd conversation tagPOSTAdds one or more tags to a conversation.
list_tagsList tagsGETLists all tags available for categorizing conversations.

Channel, 1 operation

list_channelsList channelsGETLists all channels in the company including email, SMS, social, and custom channels.

Comment, 1 operation

add_commentAdd commentPOSTAdds an internal comment to a conversation visible only to teammates.

Event, 1 operation

list_conversation_eventsList conversation eventsGETLists events that occurred for a conversation in reverse chronological order.

Inbox, 1 operation

list_inboxesList inboxesGETLists all inboxes available to the authenticated user or API token.

Teammate, 1 operation

list_teammatesList teammatesGETLists all teammates in the Front organization with their IDs and details.

Front API rate limits

120 requests per minute

Plan-based: Starter 50 rpm, Professional 100 rpm, Enterprise 200 rpm. Burst allowance equals half the plan rate limit (including purchased API add-ons); exceeded burst requests are replenished after 10 minutes. Tier 2 endpoints are additionally limited to 5 requests per resource per second, per endpoint: this covers update_conversation, update_conversation_assignee, create_conversation and send_reply. Partner integrations acting via OAuth on behalf of a company have a separate 120 rpm enforced per company.

These are the limits Front documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Front documentation for current values.

Use Front from Claude Code, Cursor or Codex

Connect Front in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Front operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Front

Create your workspace
Sign up free. Nothing to install.
Connect Front once
Add your Front connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Front integration FAQ

What can you do with the Front integration?

LiveContext exposes 20 operations on Front, covering conversation, contact, message and tag. Common uses include CRM sync, ticket assignment and conversation display.

What are the Front API rate limits?

Front documents 120 requests per minute. Plan-based: Starter 50 rpm, Professional 100 rpm, Enterprise 200 rpm. Burst allowance equals half the plan rate limit (including purchased API add-ons); exceeded burst requests are replenished after 10 minutes. Tier 2 endpoints are additionally limited to 5 requests per resource per second, per endpoint: this covers update_conversation, update_conversation_assignee, create_conversation and send_reply. Partner integrations acting via OAuth on behalf of a company have a separate 120 rpm enforced per company. Limits are set by Front and can depend on your plan.