---
ref: tool:front/assign-conversation
name: Assign a conversation
company: company:front
workflows: [workflow:shared-inbox-triage]
access: [mcp, api]
tags: [capability:route-alerts, category:support, has:api, has:mcp]
docs: https://dev.frontapp.com/reference/update-conversation-assignee
updated: 2026-09-29
---

# Assign a conversation

Assigns a conversation to a teammate, or unassigns it.

Note: Takes a teammate ID (`tea_...`), not a name, or null to unassign; find teammate IDs with `list_teammates` on the MCP server.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "front": { "url": "https://mcp.frontapp.com/mcp" } } }
```

Call the MCP tool `assign_conversation`.

Server URL: https://mcp.frontapp.com/mcp

Note: Connect with the client ID and secret of a Front developer app that has MCP Server access: Front has no dynamic client registration.

### API (official)

- Base URL: https://api2.frontapp.com
- Endpoint: `PUT /conversations/{conversation_id}/assignee`
- Auth: send the header `Authorization: Bearer $FRONT_API_KEY`
- Get a key: https://dev.frontapp.com/docs/create-and-revoke-api-tokens
- Docs: https://dev.frontapp.com/reference/introduction

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.