Front

Front is a customer operations platform for team communication.

Overview

Front is a shared inbox platform that unifies email, SMS, chat, and social messages into team-managed conversations. It is widely used by support, success, and operations teams that need to triage incoming customer communication, assign conversations to teammates, and apply tags or workflows for routing.

In Spojit, Front is most often used as both a source of customer signal and a destination for outbound replies. You can pull conversations into AI workflows for classification or summarisation, push acknowledgements back into the same thread with send-message, or fan messages out to Slack and Monday.com so the rest of the business sees them.

What You Can Do

The Front connector exposes these tools:

add-tag - apply an existing tag to a conversation.
create-contact - create a contact record with handles and groups.
get-contact - fetch a single contact by id or handle.
get-conversation - fetch a conversation with its messages and metadata.
list-contacts - list contacts with pagination and filters.
list-conversations - list conversations across one or more inboxes.
list-inboxes - list every inbox the token can access.
list-tags - list all tags configured in the workspace.
list-teammates - list teammates available for assignment.
raw-api-request - call any Front Core API endpoint directly.
send-message - send a new message or reply into a conversation.

Authentication

Front uses an API token. Generate one in Front at Settings -> Developers -> API tokens. The token inherits the scopes of the user that creates it, so create it from an account that can read every inbox you need and send messages on behalf of the team. Tokens are long-lived but can be revoked from the same page; rotate yours if a teammate leaves.

Setting Up Your Connection

In Front, open Settings -> Developers -> API tokens and create a new token.
Copy the token value (it is only shown once).
In Spojit, go to Connections from the sidebar.
Click + Add Connection and search for Front.
Paste the API token into the connection settings.
Name the connection (for example, Front - Support) and click Save.

Using in a Workflow

Use Direct Mode for predictable steps such as send-message replies or add-tag after classification. Use Agent Mode when an AI step needs to inspect a conversation, decide whether to tag, reply, or escalate, and then act. For high-volume polling of inboxes, prefer list-conversations with a date filter rather than fetching every conversation.

Tips

Cache the output of list-inboxes and list-tags at the start of a workflow rather than calling them for every conversation.
The send-message tool needs the channel_id of the channel you are sending from, not the inbox id.
Use raw-api-request for endpoints not covered by the dedicated tools, such as assigning conversations or archiving.
Front's API is rate-limited per token; keep parallel branches modest and add retry on 429 responses.

Common Pitfalls

Tags must already exist in Front before add-tag can apply them; the tool will not create new tags.
Messages sent via send-message appear from the channel, not from a teammate, so reply signatures may differ from manual replies.
The conversation id changes when messages are merged; resolve by handle (email or phone) instead of caching ids long-term.
API tokens are user-scoped, so removing the teammate who created the token will revoke it.

Common Use Cases

For technical API details and field specifications, see the Front connector documentation.