Front is a customer operations platform that enables teams to streamline communication and deliver exceptional service at scale.
Power end-to-end data operations for your Front API with Nexla. Our bi-directional Front connector is purpose-built for Front, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Front or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Front workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Front credential, you need to obtain an API token from your Front account. The API token is required to authenticate with the Front API.
To obtain your API token, you need to have a Front account with API access enabled. Once you have access to your account, you can generate an API token from your Front settings. The API token is sent in the Authorization header with the Bearer prefix (e.g., Bearer {token}) for all API requests to the Front API. For detailed information about API token setup and authentication, refer to the Front API documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Front
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Front API token in the API Key Value field. This is the API token you obtained from your Front settings. The API token is sent in the Authorization header with the Bearer prefix for all API requests to the Front API.
Keep your API token secure and do not share it publicly. The API token provides access to your Front account and should be treated as sensitive information. You can view and manage your API tokens in your Front settings. The API token is sent in the Authorization header with the Bearer prefix for all API requests to the Front API. For detailed information about obtaining and managing API tokens, see the Front API documentation.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Front connector tile, then select the credential that will be used to connect to the Front instance, and click Next; or, create a new Front credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Front endpoints. Each template is designed specifically for the corresponding Front endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
List Contacts
List the contacts of the company.
This endpoint automatically retrieves all contacts from your Front account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://api2.frontapp.com/contacts. The endpoint URL is automatically constructed based on the Front API base URL.
The endpoint uses token-based pagination, automatically fetching additional pages as needed. When a response includes a _pagination.next value, Nexla automatically uses it as the page_token query parameter for the subsequent request to fetch the next page of results.
The endpoint will return all contacts in your Front account. The response data is extracted from the _results array in the API response ($._results[*]), with each contact record processed individually.
This endpoint retrieves all contacts associated with your Front company. The endpoint uses token-based pagination (iteration.type: paging.next.token) through the _pagination.next mechanism. When a response includes a _pagination.next value, Nexla automatically uses it as the page_token query parameter for the subsequent request. The response data path is $._results[*], which extracts all items from the _results array in the API response. For detailed information about listing contacts, see the Front API documentation.
List Accounts
List the accounts of the company.
This endpoint automatically retrieves all accounts from your Front account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://api2.frontapp.com/accounts. The endpoint URL is automatically constructed based on the Front API base URL.
The endpoint uses token-based pagination, automatically fetching additional pages as needed. When a response includes a _pagination.next value, Nexla automatically uses it as the page_token query parameter for the subsequent request to fetch the next page of results.
The endpoint will return all accounts in your Front account. The response data is extracted from the _results array in the API response ($._results[*]), with each account record processed individually.
This endpoint retrieves all accounts associated with your Front company. The endpoint uses token-based pagination (iteration.type: paging.next.token) through the _pagination.next mechanism. When a response includes a _pagination.next value, Nexla automatically uses it as the page_token query parameter for the subsequent request. The response data path is $._results[*], which extracts all items from the _results array in the API response. For detailed information about listing accounts, see the Front API documentation.
List Channels
List the channels of the company.
This endpoint automatically retrieves all channels from your Front account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://api2.frontapp.com/channels. The endpoint URL is automatically constructed based on the Front API base URL.
The endpoint does not use pagination and returns all channels in a single request.
The endpoint will return all channels in your Front account. The response data is extracted from the _results array in the API response ($._results[*]), with each channel record processed individually.
This endpoint retrieves all communication channels configured in your Front account. Channels represent the different ways your team communicates with customers (e.g., email, phone, chat). The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $._results[*], which extracts all items from the _results array in the API response. For detailed information about listing channels, see the Front API documentation.
List Events
Lists all the detailed events which occurred in the inboxes of the company ordered in reverse chronological order (newest first).
This endpoint automatically retrieves all events from your Front account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://api2.frontapp.com/events. The endpoint URL is automatically constructed based on the Front API base URL.
The endpoint uses token-based pagination, automatically fetching additional pages as needed. When a response includes a _pagination.next value, Nexla automatically uses it as the page_token query parameter for the subsequent request to fetch the next page of results.
The endpoint will return all events in your Front account, ordered from newest to oldest. The response data is extracted from the _results array in the API response ($._results[*]), with each event record processed individually.
This endpoint retrieves all detailed events that occurred in your Front inboxes. Events represent various actions and changes in your Front account, such as message sends, replies, assignments, and status changes. Events are returned in reverse chronological order (newest first). The endpoint uses token-based pagination (iteration.type: paging.next.token) through the _pagination.next mechanism. When a response includes a _pagination.next value, Nexla automatically uses it as the page_token query parameter for the subsequent request. The response data path is $._results[*], which extracts all items from the _results array in the API response. For detailed information about listing events, see the Front API documentation.
List Conversations
List the conversations in the company in reverse chronological order (most recently updated first).
This endpoint automatically retrieves all conversations from your Front account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://api2.frontapp.com/conversations. The endpoint URL is automatically constructed based on the Front API base URL.
The endpoint uses token-based pagination, automatically fetching additional pages as needed. When a response includes a _pagination.next value, Nexla automatically uses it as the page_token query parameter for the subsequent request to fetch the next page of results.
The endpoint will return all conversations in your Front account, ordered from most recently updated to least recently updated. The response data is extracted from the _results array in the API response ($._results[*]), with each conversation record processed individually.
This endpoint retrieves all conversations in your Front account. Conversations represent threads of communication with customers and are ordered by most recently updated first. The endpoint uses token-based pagination (iteration.type: paging.next.token) through the _pagination.next mechanism. When a response includes a _pagination.next value, Nexla automatically uses it as the page_token query parameter for the subsequent request. The response data path is $._results[*], which extracts all items from the _results array in the API response. For detailed information about listing conversations, see the Front API documentation.
List all company rules
List the company rules.
This endpoint automatically retrieves all company rules from your Front account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://api2.frontapp.com/company/rules. The endpoint URL is automatically constructed based on the Front API base URL.
The endpoint does not use pagination and returns all company rules in a single request.
The endpoint will return all company rules in your Front account. The response data is extracted from the _results array in the API response ($._results[*]), with each rule record processed individually.
This endpoint retrieves all company-level rules configured in your Front account. Company rules define automated workflows and actions that apply across your entire organization. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $._results[*], which extracts all items from the _results array in the API response. For detailed information about listing company rules, see the Front API documentation.
List Rules
List the rules of the company.
This endpoint automatically retrieves all rules from your Front account. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://api2.frontapp.com/rules. The endpoint URL is automatically constructed based on the Front API base URL.
The endpoint does not use pagination and returns all rules in a single request.
The endpoint will return all rules in your Front account. The response data is extracted from the _results array in the API response ($._results[*]), with each rule record processed individually.
This endpoint retrieves all rules configured in your Front account. Rules define automated workflows and actions that can be applied to conversations, messages, and other Front resources. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $._results[*], which extracts all items from the _results array in the API response. For detailed information about listing rules, see the Front API documentation.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Front data sources can also be manually configured to ingest data from any valid Front API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Front API endpoints typically follow the pattern https://api2.frontapp.com/{endpoint_path}. The endpoint requires API Token authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. For detailed information about Front API endpoints and available APIs, see the Front API documentation.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Front data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Front destination, and select the Send to Destination option from the menu. Select the Front connector from the list of available destination connectors, then select the credential that will be used to connect to the Front organization, and click Next; or, create a new Front credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Front endpoints. Each template is designed specifically for the corresponding Front endpoint, making destination setup easy and efficient. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create Contact
Create a new contact.
This endpoint automatically creates a new contact in your Front account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses POST requests to https://api2.frontapp.com/contacts. The endpoint URL is automatically constructed based on the Front API base URL.
The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the contact data to create.
Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a contact. If you need to create multiple contacts, you can send multiple records, but each will be processed as a separate request.
This endpoint does not automatically create a data source to track the responses received from the Front API after each call.
The request body must be properly formatted JSON that matches the Front API specification for creating contacts. The endpoint requires API Token authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating contacts, including required fields, field names, and request formats, see the Front API documentation.
Front destinations can also be manually configured to send data to any valid Front API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Front API endpoints typically follow the pattern https://api2.frontapp.com/{endpoint_path}. The Front API typically expects JSON format for request bodies. The endpoint requires API Token authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. For detailed information about Front API endpoints and available APIs, see the Front API documentation.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Front endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Front endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
