Developers

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

Hi,We want to detect order numbers such as PO-123456, PO123456, or PO 123456 in a conversation using an application object. What would the pattern look like? Do I need to create 3 separate application object features?Best Regards

How come we are unable to link anything and everything? I have 2 conversations linked, but I want to link a 3rd conversation with the non-original, but can’t.

Join Front’s community team for three hands-on Connectors workshops in January! Follow along as we automate workflows between Front and your 3rd-party tools. January 15: Salesforce <> Front workflows: Use Connectors to update Salesforce objects directly from your inbox. January 22: HubSpot <> Front workflows: Use Connectors to easily manage customer data in HubSpot. January 29: Jira <> Front workflows: Use Connectors to create Jira tickets from Front with just a few clicks. Register nowCan’t make it? No p

We're excited to announce the launch of our new API analytics dashboard! You can now get a visual overview of your Core API request patterns and rate limiting directly in Front. This dashboard makes it easy to monitor your Core API consumption over time, quickly identify which endpoints are generating the most traffic, and spot where you might be hitting rate limits—all without having to piece together information from logs or error messages.  The dashboard features interactive time-series charts showing your total Core API calls (with rate-limited requests clearly highlighted) and an endpoint breakdown table that shows usage by path, including call counts and rate limit hits. 

We're thrilled to announce a major improvement to how you build macros with Connectors: app request nodes are now available in your flow builder. No more hunting through dynamic variable menus or trying to figure out where to nest your app requests inside action nodes. You can now drop an app request directly into your macro flow by clicking the plus (+) sign and selecting "Send app request"—just like any other node. This makes building Connector-powered workflows far more visual and intuitive.View the docs for step-by-step instructions!  

You can now configure pagination for application requests! When enabled, the dynamic dropdown in macros loads data page by page as the user scrolls—making it easy for customers to work with larger data sets—no additional macro configuration required. If a dropdown’s app request is paginated (or gets converted to one), the scrolling behavior automatically kicks in for Front teammates. In combination with creating structured, multi-step macros that capture teammate answers, you can now build robust workflows that allow you to execute actions in external systems for the exact item you want to modify. Example use cases:Searching through customer records in a CRM Selecting from a product catalog in an external inventory system Choosing the correct order to refund for a

We've just released an AI prompt file that lets you scaffold Front plugins using any AI coding agent—Claude Code, GitHub Copilot, ChatGPT, Cursor, and more.Simply describe what you want your plugin to do, and the AI generates a working plugin that follows best practices, correctly uses the Front Plugin SDK, and includes built-in debugging tools. What used to take hours of learning our SDK now takes about 10 minutes.Why this matters:Speed - Get from idea to working plugin faster than ever Correctness - The AI handles Front-specific patterns and boilerplate automatically Accessibility - Lower barrier to entry—you don't need to be a Front SDK expert to get started Best practices - Ensures plugins follow established patterns for Front data models and context handling from day one Debugging - Built-in tools show exactly what's

The icons for developer apps will now have squared off edges rather than a circular design. This new look aligns with our updated design principles and brings more consistency across the app.You can set the icon in the Settings tab of your developer app:And you’ll see it in Front in places like the list of developer apps and in the rule, macro, and other workflow menus where you select to use a feature from your developer app, such as a channel or app request (Connector).  

Hi,We’ve started receiving 400 Bad Request errors when calling the conversations/search endpoint. A request such as:https://api2.frontapp.com/conversations/search/after:1762920938801 now returns:400 Bad Request {"_error":{"status":400,"title":"Bad request","message":"Unsupported search modifier provided."}} We aren’t using any other modifiers, and there have been no changes on our side. The issue began on 23 July 2025. From what I can see, using after: is still documented and there’s nothing in the changelog that suggests this behaviour should have changed.Do you h

Hi everyone,I'm building an automation using n8n together with the Front API, and I'm running into a major challenge regarding attachment ordering inside a Front draft. I would really appreciate deeper clarification from the community or the Front team, because this is critical for my use case.ContextI'm a service provider and we onboard customers into different training programs. Each onboarding email contains multiple PDF attachments in a fixed order.From these files: 6 documents are always the same and are already included inside a Front Message Template 3 documents are unique per customer (contract, schedule, and one additional document), and these three files are generated dynamically in n8n and added to the draft in the same step after the template content is applied Because of this setup, I rely on a Front template for the 6 standard documents, and n8n is responsible for attaching th

I am attempting to build a sidebar plugin in Retool so I can utilise all of my existing modules, components, and queries so I can surface important contextual information for my CS team.We all use Google sign in to login to our Retool apps, and we are having a few problems inside Front’s sidebar due to third party cookies.The native Retool sign in screen does not/cannot pop up the Sign in with Google page so I get the below 403 error when I click “Sign in with Google”  I have now tried to create a public Retool app, that just has a single “Sign in with Google” button on it (which is just a Retool button), which calls the following script on click: console.log("Front.o

I am setting up an integration and using the teammate groups API.I can successfully create a teammate group and fetch it by id: POST /teammate_groups returns 201 with an id like cir_xxx GET /teammate_groups/cir_xxx returns the full group object  But when I call:GET https://api2.frontapp.com/teammate_groups Authorization: Bearer <token> Accept: application/json  I always get:{ "_links": { "self": "https://api2.frontapp.com/teammate_groups" }, "_results": [] }  Same behavior if I use the company host https://company.api.frontapp.com. The same admin token is used for create, get by id, and list, and other endpoints like GET /teams work fine. Am I missing something about how GET /teammate_groups works, or is this a bug with the listin

Check out our new video walkthrough for how to use Connectors to process Stripe refunds directly from Front! Make sure to subscribe to the Connectors space for more examples!

I have a tool that POST a draft, with a body formatted in HTML like:“<p>Based on the information provided, we are pleased to offer you a quote of:</p><ul><li>Transport: EUR <strong>200</strong> (Excl. VAT)</li><li>Insurance (optional, on declared value) : EUR <strong>20</strong> (Excl. VAT)</li></ul>”When I visualize the draft created in Front (app or web browser), I see a blank line before the list:When I inspect the object, I see a <br></br> balise, which was not in the original HTML.This disappears when I’m viewing the draft as another person (viewer mode).And so when I send it, the blank line remains.. This is quite problematic as it gives something weird visually.