Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: API key.
  • Connection: The key from FRONT_API_TOKEN is sent as the Bearer prefixed Authorization header.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. Get a Front account: Sign up at https://front.com - a free trial workspace is enough for testing. You can also request a developer sandbox at https://dev.frontapp.com.
  2. Create an API token: In Front, open Settings → Developers → API Tokens and click ‘Create API token’. Give it a descriptive name and pick the scopes you need (read access for browsing, plus shared resource access to send replies). Admin privileges are required to manage tokens.
  3. Store the token: Add FRONT_API_TOKEN=<your token> to your .env file. Requests authenticate with the header ‘Authorization: Bearer <token>’ against https://api2.frontapp.com.
  4. Verify access: Run the List Inboxes tool. You should get back the inboxes your token’s scopes can see.

​
Provider notes

  • Replying to a conversation archives it by default - pass options { “archive”: false } to keep it open
  • Message sending is asynchronous: the reply endpoint returns 202 Accepted with a message_uid rather than the final message
  • API tokens are scoped at creation time; a token without the messaging scopes can read conversations but not send replies
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as front__list_conversations with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.