Developers

We're excited to announce that the Front UI Kit is now fully compatible with React 19! This update ensures that our components and Storybook are aligned with the latest major React revision, allowing you to take advantage of React 19's new features and improvements. To update run npm install @frontapp/ui-kit@latest or yarn add @frontapp/ui-kit@latestMake sure you are using React 19 before upgrading the Front UI Kit React 19 introduces several enhancements that improve app performance, developer experience, and component flexibility. Our team has diligently tested and updated our UI Kit to ensure smooth integration and optimal functionality with this major React release. For those who aren’t familiar, the Front UI Kit is a set of React components that hel

This change contains a deprecation of the external_conversation_id property in the metadata object.You can now reply to specific messages through application channels.{ "type": "message", "payload": { [MESSAGE BODY] }, "metadata": { "external_conversation_ids": string[], // External identifier of the conversations related to this message. "referenced_message_external_id": string // (Optional) ID of the message being referenced as a direct reply }}As part of this change, we are introducing two new properties in the metadata object used when creating or replying to messages in a channel:external_conversation

I ran into internal error 500 when trying to use attachments. Even If I don’t use attachments and just Content-type multipart/form-data it returns error anyway.postmanpostmanwith code (wordpress)[headers] => WpOrg\Requests\Utility\CaseInsensitiveDictionary Object        (            [data:protected] => Array                (                    [date] => Sun, 03 Aug 2025 06:23:15 GMT                    [content-type] => application/json; charset=utf-8

Hi everyone, Has anyone here built a custom integration between Front and a cloud contact center solution?We’re looking to:Display incoming voice call context in Front Sync call metadata (duration, caller ID, agent notes)

 I have an image in signature. When sending from admin image is shown correctly and has attribute data-image-whitelisted. But when using API it is brokenfrom API$url = 'https://api2.frontapp.com/channels/' . $channel_id . '/messages'; $body = array( 'to' => array( $to ), 'subject' => $subject, 'body' => $content, 'text' => wp_strip_all_tags( $content ), 'options' => array( 'archive' => false, ), 'author_id' => 'tea_j7twg', 'signature_id' => $signature_id, ); $args = array( 'method' => 'POST', 'headers' => array( 'Authorization' => 'Bearer ' . $api_token, 'Content-

You can now configure servers with variable subdomains. This enables your apps to connect to APIs with customer-specific endpoints (e.g. Salesforce, Shopify, Netsuite) or support different regions or production environments. During setup, the developer specifies what part of the origin is a variable, and then during installation of your app, Front admins supply the specific subdomain value. Happy coding!

I want to access the data used to calculate handle time for my team which to my understanding isn’t included in the fivetran schema that I’m currently using to connect to the database. Which API end point do I need to interact with to get this? I understand the logic used to calculated handle time but what are the fields (i.e. date, interval) used called and how can I find them? 

Hello! I encountered a problem where https://dev.frontapp.com/reference/plugin-sdk-context doesn’t work as expected. Here I depicted a plugin usage scenario that went wrong.After page reloading the plugin is opened by default, and we see only 1 email attached to the user. At this moment, the issue is not visible. Next, we’re navigating to the Contact Details tab to check how many emails the user has in real. And we’re confusing that the user has 2 emails, not 1 as plugin Context said.  However, upon returning to the plugin, it correctly displays the information with 2 emails.To read this information I use  context.conversation.recipient.contact.handles Please take a look this bug, it causes problems in buil

We’ve added ticketing concepts to the Plugin SDK so you can easily view and manage conversations for companies that have this feature enabled. The new method and data model updates should help navigate Front ticketing within your plugins without having to call the Core API. To grab the latest version, run npm install @frontapp/plugin-sdk@^1.9.0 --save or bump your package version manually. If using Yarn, run yarn upgrade @frontapp/plugin-sdk@^1.9.0. The Plugin SDK now offers the following additions:A new listTicketStatuses method that returns the ticket statuses available for the company. The Conversation model in the Plugin SDK

Build more flexible Connectors by adding multiple requests to your configuration—all within a more intuitive visual interface.  We’ve redesigned how you build Connectors in Front, moving from a rigid step-by-step setup to a flexible flow builder. This new visual interface gives you greater control when connecting Front to external APIs and systems using application requests and application objects.With the new visual flow builder, you can now add multiple requests within a single Connector configuration. Whether you're retrieving data from different endpoints or chaining act

Hello,We are looking for a developer to help us migrate 6000 email conversation as well as 10 inboxes (and some tags and contacts) over to a different Front account. We have been using Front for a year through a third-party company that we pay to perform customer service duties, but we now want to do this in-house and are looking to open our own account.

Hello, I would like to ask if it is possible to display the typing indicator while waiting for a response from the API, and secondly, how can I authorize the client logging in to the chatbot via SMS?

The first two steps in the documentation to make an app are to go to settings, click on company, and then click developers. However, I can’t see developer as an option and nothing appears on the search bar either when I search for developer. I have been granted admin permission from the company (received it a few hours ago). Sorry if this is a really silly question to ask just no idea how to continue from here. 

Are you planning to add support for Expo for React Native in the future?Our team uses Expo to build and ship our mobile app, and we’ve historically used Intercom (which already has an Expo plugin). We’re considering switching to Front but the lack of Expo support makes the potential switch a big headache.

initially I thought adding the inbox access to the newly created teammate group would work but I get an error that Team access is required to link to team inboxes. I find it odd that I can create a teammate group via the API but cant actually add inbox permissions without a manual step in between? Any insight would be appreciated, just want to make sure I am not missing something.  Thank you! 

We have a Front integration that involves fetching conversations within a timeframe from selected inboxes, at the moment we paginate through the conversation search endpoint for each inbox ID. However, to ensure that we fetch all the conversations in that timeframe it would be much easier for us if the inbox filter was treated as one of the `OR` filters (from, to, cc, bcc) so that we could filter `inbox:A inbox:B after:<date> before:<date>`

I’m looking for a way to include a link that users can click on to compose a new Twilio SMS in Front. Ideally it would work similar to clicking the phone number on a contact record (where it opens a compose window with the To: field already pointing to the phone number.  Is this possible today? It would be great if it was possible to just have a link like app.front.com/compose?type=sms&to=1234567891 but I’m also open to using the core API to create a new conversation and then link to that conversation.  

You should now see a fresh look and feel to the UI when you navigate to Settings > Developers. These changes were made to help you manage features on your developer apps more quickly. The Apps list now displays the features associated with each of your apps:When you click into an app, you will see that the Features tab now lists all the app’s features so you can easily manage them without having to click into each feature card like you did in the old experience.The OAuth tab has been moved into the Features list. It was previously a top-level tab. When you click Add

You can now reply to specific comments using the Core API. Comment replies visually indicate which comment is being responded to, helping users follow the conversation. This feature has been available in the Front UI for a long time, but is now available via the API. Use the Add comment reply endpoint to create a comment reply. Happy coding!

The is_spammer property is no longer part of the Contacts response. This property was deprecated a few years ago but is now fully removed from the response object. No issues are expected, but if you notice any, please leave us a comment or reach out to our Support team.

I want to have my own button placed on page, on click it opens chat widget. And when chat is closed, again set iframe to 1px height and width. I didnt find any events for this.var chatFrontLoaded = false; let chatBtnFront = document.querySelector(".spider-front-chat-btn"); chatBtnFront.addEventListener("click", function(e) { e.preventDefault(); if(!chatFrontLoaded) return; window.FrontChat("show"); }); setTimeout(()=>{ window.FrontChat("init", {chatId: "",shouldHideExpandButton:true, useDefaultLauncher: true, onInitCompleted: () => { chatFrontLoaded = true; window.FrontChat("hide"); const chatIframe = document.querySelector("#front-chat-iframe"); chatIframe.style.height = "1px"; chatIframe.style.width = "1px"; }}); if(chatFrontLoaded) { } }, 1500);It is also very sad that I need wrap i

I created an API key: https://app.frontapp.com/settings/developers/tokensI use that API key to create an emailSometime that email is assigned to that API key like it’s a teammate, but sometime it doesn’t. I didn’t even knew that we could assign a conversation to an API key.I expect that email to be assigned to no one.

Application triggers allow you to execute workflows in Front in response to events that occur in external systems. For example, you might want to re-open conversations in Front anytime an order changes status. When the event occurs in your order management system, you send Front an event payload identifying the trigger for the change of order status. The event payload would also identify an application object, likely through the link to the order in your management system. Once the trigger is received, any conversations that have a related application object attached for the order would reopen based on a rule. Your rule could also pull additional properties from the trigger's event payload, such as the new status, and make that available through a dynamic variable. The additional data from the property could apply a comment or tag or other action in Front based on the new status. To learn how to use application triggers, refer to our Developer Portal:

Hello, I'm developing a plugin for composer mode and I need to edit the current draft.As I understand from looking at the documentation, I need to make an API call with the message id of the draft in the url which is "msg_" but from the context in composer mode what I get is a draft id like "dra:***".I thought about making an API call first to list the messages of a conversation since I do get the conversation id from the context and from there extract the msg_ of the message if it has a draft. The problem I find is when there are several active drafts in a conversation since I only want to edit the draft of the user who is using the plugin.Is there any way to get the msg_ of the current draft through the context in composer mode?Thanks very much in advance.

You can now open a sidebar plugin from URLs found in Front messages or comments. The format for doing so is:Syntaxhttps://<Front base domain>/open-sidebar-plugin/<App UID>Examplehttps://app.frontapp.com/open-sidebar-plugin/40a4eae201a760d1 Pass custom properties to your pluginYou can pass custom properties in the URL as query string parameters, which will then become available to your plugin’s context in the EntryPoint object.https://app.frontapp.com/open-sidebar-plug