Front
Read and update Front conversations, messages and comments, send replies, and manage contacts, accounts and tags.
Bring shared-inbox conversations and customer accounts into CRM, order and operations flows.
Source actions
12
Destination actions
9
Data types
11
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
accounts
- Create accountDestinationNot retried automatically
Creates a customer account.
- List accountsSource
Customer accounts (companies) with domains and custom fields.
- Update accountDestinationDuplicate protected
Updates an account's name, domains, external ID and custom fields.
comments
- Add commentDestinationNot retried automatically
Adds an internal comment to a conversation.
- List conversation commentsSource
Internal teammate comments on a conversation.
contacts
- Create contactDestinationNot retried automatically
Creates a contact with handles, links, lists and custom fields.
- Get contactSource
A contact by ID or alias such as alt:email:ada@example.com.
- List contactsSourceIncremental
Contacts with handles and custom fields, oldest update first when filtered.
- Update contactDestinationDuplicate protected
Updates a contact's name, description, links and custom fields.
conversation tags
- Tag conversationDestinationDuplicate protected
Adds tags to a conversation without removing existing ones.
conversations
- Get conversationSource
A conversation with assignee, tags and custom fields.
- List conversationsSource
Conversations ordered by last activity, optionally filtered by status.
- Search conversationsSourceIncremental
Conversations matching Front search syntax; Updated since adds an after: filter on activity.
- Update conversationDestinationDuplicate protected
Assigns, archives or reopens, moves inbox, sets ticket status, tags or custom fields.
custom fields
- List custom fieldsSource
Custom field definitions for contacts, accounts or conversations.
inboxes
- List inboxesSource
Shared and private inboxes the token can access.
messages
- List conversation messagesSource
Inbound and outbound messages in a conversation.
replies
- Reply to conversationDestinationNot retried automatically
Sends a reply in a conversation through its channel.
tags
- Create tagDestinationNot retried automatically
Creates a company tag.
- List tagsSource
Company tags.
teammates
- List teammatesSource
Teammates with email, availability and admin flag.
Authentication
API token
Plans and access
API tokens are available on Front plans with API access (Growth and above). Company API tokens are scoped to shared or private resources and read or write permissions chosen at creation.
Test environment
Front free trials and developer environments can be used for testing.
Rate limits
Per-company limits by plan (50–200 requests per minute plus burst); search runs at 40% of the limit; HTTP 429 with Retry-After.
Provider events
Front application webhooks and rule-based webhooks for conversation events. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Conversation deletion (status deleted), contact and account deletion are not implemented.
- Merged conversations answer with HTTP 301; Nexra does not follow redirects, so use the new conversation ID.
- Replies are accepted asynchronously (HTTP 202) and return a message UID.
- Front documents no idempotency key: replies, comments, contacts, accounts and tags are not repeated automatically when uncertain.
- Search queries cannot contain a slash.