Developers

I am currently using the Front sdk updateDraft function in the updateMode: ‘replace’ when I run it with only the subject defined, all attachments on the draft get deleted.  await sdk.updateDraft(draftId as Parameters<FrontSdk['updateDraft']>[0], { updateMode: 'replace', subject: subject });This is the current code I am using.

Hello, I need a way to add custom headers into a rule webhook call, in order to call internal routes that need API keys.The solution we found was to provide the API key directly into the path parameters, but that makes it so the key leak internally in our logs. Also, making the route key-less is not an option for us.

Hi everyone, nice to meet you!I have two questions regarding analytics reports:1 Metrics showing 0:When I request a report with:metric_names = ["num_messages_sent", "num_messages_received"]start_dt = datetime(2025, 8, 10, 0, 0, 0)end_dt = datetime(2026, 3, 1, 0, 0, 0)account_id = [account_id]I get:'metrics': [ {'id': 'num_messages_sent', 'type': 'number', 'value': 0}, {'id': 'num_messages_received', 'type': 'number', 'value': 0}]However, when I manually check the contacts and conversations for this account, there are messages sent in that interval. I don’t understand why the report shows 0. Here is my code if it helps:metric_names = ["num_messages_sent", "num_messages_received"]start_dt = datetime(2025, 8, 10, 0, 0, 0)end_dt = datetime(2026, 3, 1,

I am working on a project that requires I pull data from our in house database and run reports from those and send them automatically to the respective managers that requires the report. We run these reports weekly. I would like to use Parabola to run the emails through Front. Is this something anyone has had experience with and have any thoughts on how this worked or didn’t work for you?

How can I link a message or conversation to another conversation, just like I can do it from the UI using the "Link to original" button?  I know how I can link conversations, but it's not the same as when it's done via the UI. I need to do this via the API, and there simply doesn't seem to be any option to do this. When I look through the API docs and I link the conversation, then it is just added on top as an external link, but I wanted to be internally linked within the conversation around the original conversation, just like I do it from the UI.  How would I use the API to do this? 

It appears like Model Context Protocol (MCP) is the protocol that everyone is moving towards as it puts the burden of keeping everything “tidy” on the service provider rather than the client.  There are already many official MCP servers available and more on the way. There are also community developed ones. Is anyone else exploring this?Cheers!

Hi Front team 👋We have a plugin which is created using @frontapp/ui-kit, and we’ve run into a limitation regarding dark theme support.At the moment, most (if not all) component colors in the UI Kit appear to be hardcoded. Because of this, there’s no straightforward way to support a dark theme in our plugin without overriding the existing component styles.While overriding styles is technically possible, it doesn’t feel like a clean or sustainable solution, especially considering future updates to the UI Kit.We’d like to ask: Are there any plans to introduce official dark theme support in @frontapp/ui-kit? Is there (or will there be) a theming system using design tokens, CSS variables, or similar approaches? What is the recommended best practice for supporting dark mode in Front plugins today?

Hi everyoneWe’re exploring ways to integrate our cloud contact center solution with Front and wanted to see what others here have done. Specifically, we're hoping to streamline agent workflows by syncing conversations, contact data, and possibly call recordings into Front.Has anyone here integrated Front with platforms like:Genesys Cloud WebEx Contact Center Talkdesk Five9

 If you’re a customer or partner who has been using our APIs, SDKs, Connectors, channels, or any other platform touchpoint to build integrations or improve your workflow automations, we’re looking to partner closely with you to take your existing usage to the next level. Interested? Become one of our design partners: 

You can now add query string parameters to Connectors using a handy table. While you can still type query string parameters directly into the URL, the table makes it easier to see the parameter names and values, especially when you have multiple parameters. The URL has also been split into two rows (one for the domain and one for the rest of the endpoint) so that it’s easier to manage longer paths. This update applies to both application requests and application objects. We hope you enjoy it! 

You can now configure your app webhooks to use an authenticated server instead of a plain URL. While these requests have always been signed—which lets you tell if some imposter sent the notification instead of Front—they now can be authenticated, too.When you set up application webhooks with a server, customers will supply unique credentials when installing your published app:Allowing your webhook server to identify exactly which customer each event pertains to Meeting enterprise security requirements  One thing to note: Webhooks will fail to send if customers skip the Authentication tab during install, so make sure your setup guide tells them to complete it. Check out our webhooks documentation to get started.

Learn how to add search and pagination parameters to your app requests in order to power dynamic dropdowns in macros. These dropdowns allow your teammates to search for and scroll through a relevant list of results in order to select the external record they’re interested in. The walkthrough uses searching for charges in the Stripe API as an example.View the example below:  

You can now manage views programmatically via the Core API. Views are custom work queues that filter conversations by inboxes, tags, and assignees—helping users track high-priority conversations and ensure nothing goes unanswered. What you can do:List all views accessible to your token, or filter by teammate, team, or company Get, create, update, and delete views Configure filtering criteria including inbox IDs, tag IDs, and assignee IDs Add views to specific teammates' sidebars to make them visible in their navigationCommon use cases:Provision custom views for new team members during onboarding Standardize views across teams to ensure consistent workflows Dynamically create views based on external data or business logic Pin important views to teammates' sidebars automatically Manage views at scale across your organization

You can now permanently delete conversations via the Core API using the new Delete conversation endpoint. Key details:Conversations must have status trashed before they can be permanently deleted This action cannot be undone Requires the conversations:delete scope Check out the full documentation for implementation details.

We're excited to announce that the Core API now supports granular permissions for API tokens and OAuth tokens. You now have fine-grained control over what your tokens can access and modify, helping you follow the principle of least privilege and improve your integration's security.  How It WorksWhen you configure a token, you'll specify Features (what functionality the token can use), Namespaces (the scope of resources it can access), and Permissions (what actions it can perform for each resource it has access to). Granular PermissionsYou can now granularly control access for each resource type:Read – Retrieve resource information Write – Create and update resour

We are really struggling with this.Our goal is to receive a list of ‘open’ conversations in our personal inbox. This includes direct messages AND a any conversation that we are subscribed to (participant of) both in Shared Inboxes and Teammates Inboxes.However there’s an inherent problem: is:open is not useful whatsoever… Because status: “archived” is global, when a user outside of our personal inbox ‘archive in my inbox’ that status is now status:archived…This means I have to search for status:archived to see basically all my conversations (thousands) and find a way to figure out which ones are actually open in my view… we’ve tried /conversations/{id}/followers to see if i’m attached to that conversation, looking at conversation events… but its just not easy. If we had open graph or something maybe that would help…Does anyone know how to deal with this ‘global’ archiving issue, I should be able to see what my Front UI shows..

We have API integration with FrontApp for many years using our live account. We need to build an application channel for internal use only that will be used to handle specific type of group messages not currently supported by FrontApp.I already setup the developer app and application feature is installed. The app is verified and the webhook is working when I create messages on FrontApp directly.I am trying to sync an external message back into the channel, but I am getting this error“Only partners can access channels. Please see https://dev.frontapp.com/docs/channels-overview for access.”I looked at the documentations and it requires the app to be developed before I can get a partner account, but I can’t develop the app if I can’t sync the messages.Again, this is for internal use only. The reason we are choosing application app instead of custom channels is custom channels can’t "Compose new outbound messages with replies threaded in the same conve

Hi allI’m looking to save emails (and attachments) from conversations in Front to my software using its API. I’ve created application requests and can send and receive data with them. I can create a new document in my software using a Front macro but the document is empty, because I don’t know what I should use in Front to save the email and attachments too.Hoping for some pointers!Thanks

We are experiencing issues with long automated messages failing to send.There are carriers that take the long messages and carriers that don’t - we want to just retry the ones that fail. I get that I can circumvent this problem by splitting the long message into multiple small messages and send them separately. But since most of the times the messages are delivered, we don’t want to have to split successful messages because of a few unsuccessful ones.After the message is sent, I am using this endpoint to fetch the message again:"https://api2.frontapp.com/messages/{message_id}”What I want is to see if it errored or not. The issue is that I am getting the field ‘Error Type’ empty even for failed messages.Anyone has any advice here? How can I get from the API the error status of a message?

We are using a front webhook for “all incoming messages” and forward these to our own endpoint. I need to filter out ONLY NEW conversations somehow but it seems quite tricky looking at the webhook payload. We only have a professional account (and wont upgrade to enterprise any time soon). How could I reliably filter out all replies and follow up emails and only keep NEW conversations when processing the webhook event?

Summary Enable creating and managing comment reactions (emoji reactions) via the Front API, similar to how reactions work in the Front UI.Current State The Front API currently supports:Creating comments on conversations Editing existing comments Listing commentsHowever, there's no endpoint to add, remove, or list reactions on comments.Requested FunctionalityPOST /comments/{comment_id}/reactions — Add a reaction to a comment DELETE /comments/{comment_id}/reactions/{reaction_id} — Remove a reaction Include reactions in the comment object when fetching commentsUse Case: AI Agents AI agents that assist support teams need lightweight ways to acknowledge information without adding noise to the conversation thread. Reactions are ideal for this:Acknowledgment signals — An