Skip to main content

Developers

Welcome to the Front Developer Community

    console.log(‘Hello Front developers!!!’);We’re excited to see what integrations you will build. We hope that this community will help you get up and running with the Front Platform as quickly as possible. Use it to get the help you need, share your ideas with us, and connect with your peers.Mission StatementEnable developers to happily build successful integrations on the Front Platform. Step 1: Take a quick tour through our community Got a technical question?Make use of our awesome search function 🔎 You can find it at the top of every page. Still not finding what you need? Post a question to our Developer Q&A.Have API feedback?Let us know how we can improve our APIs.Want to know what we’ve been working on?Subscribe to our News & Updates section to get the latest news about the Front APIs and SDKs, including deprecations that may impact your integrations.Have something interesting to share or discuss?Create a new topic in our Developer Discussion space. Step 2: Customize your profile and introduce yourself!Go to your profile settings to add a profile picture, tell us a little bit about yourself, and add a signature. When you’re happy with how your profile looks, introduce yourself to the community! Step 3: Employ our Top TipsJoin the party—Don’t be shy! Join our community and post any question, discussion, or idea you have. The more the merrier! We highly recommend subscribing to our News & Updates section so that you learn of important API updates and deprecations, and to subscribe to any other spaces that you regularly participate in.   Be detailed—Include as much information as possible in your question or post to increase the chances of a quality reply.   Keep control of your data—Don’t post private information (customer or employee data, for example). This is a public space!   Stay patient—Sometimes it might take a little while to receive the best answer, although our community does its best to reply with as little delay as possible. While you’re waiting, please refrain from posting duplicate questions in other categories.   Avoid syntax errors—Have fun, but never at anyone’s expense. Please refer to our Terms & Conditions before creating your first post or reply. Happy coding!    

Featured topics

PLATFORM UPDATE

Fresh look for developer app icons

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).  

CONNECTORS

New tutorial for processing Stripe refunds with Connectors

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!

PLUGIN UPDATE

Build Front plugins in minutes with AI!

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 being sent to your plugin during developmentWe've built three example plugins using the prompt—a NetSuite manager, subscription manager, and attachment encryptor—to show you what's possible and give you reference implementations.Check out the guide and example plugins

TUTORIAL

Solving API Timeouts with Connectors + Application Triggers

Solving API Timeouts with Connectors + Application TriggersWe've published a new workflow tutorial that shows how to handle a common integration challenge: what happens when your external system takes longer to process than Front's API timeout allows?The scenario: You trigger an API call from Front (creating an order, generating a document, processing a complex workflow), the record is created successfully in your external system, but Front times out before receiving the response. Your downstream automations never fire because Front never got the critical data back, such as the new order’s unique identifier.The solution uses a callback pattern combining:App requests (Connectors) to initiate the process via macros App objects (Connectors) to mark conversations waiting for data Webhooks from your external system when processing completes Application triggers to receive that data back into Front Rules to execute your downstream automationsWe walk through a complete end-to-end example using a transportation management system, but this pattern works for any industry where external processing times are unpredictable: complex CRM workflows, document generation, approval chains, compliance systems—anywhere you need bulletproof automation regardless of processing time.Read the tutorial  Have questions about implementing this in your workflow? Drop them in the comments. This is a powerful pattern with several moving parts, and we're here to help you adapt it to your specific use case. 

APPLICATION CHANNEL UPDATE

You can now create message templates for your application channels!

We’re excited to introduce application channel message templates in Front, designed to streamline your messaging workflows by enabling template synchronization directly from your external services. This feature offers a robust solution for maintaining consistency and efficiency in your communication channels, providing a seamless way to sync message templates created in external services (such as WhatsApp, Facebook, Google, etc.) into Front for use with your application channels.A WhatsApp message template synced into a Front application channel Application message templates are supported through two new API endpoints:Sync application message template for importing external templates for the first time Update application message template for propagating updates to existing templates  To get started, ensure you have enabled the Templates checkbox in your application channel settings within your developer app. The templates are configured in the external service (such as WhatsApp, Facebook, or Google) and synchronized to Front using the Channel API. These templates can include variables that are dynamically replaced with Front-specific values when sent, offering a high degree of customization. We're confident that this new feature will significantly enhance the messaging capabilities of your application channel, making your communications more efficient and personalized. Please let us know if you have any feedback! And as always, happy coding! 

CORE API UPDATE

Announcing 3 new event types!

Front now sends 3 new event types:ticket_status_update—sent when a ticket changes statuses. topic_identified—sent when a new topic is identified by Front AI.  macro_triggered—sent when a teammate runs a macro.Refer to the Events topic in our Developer Portal to learn how to use these events. We hope these new events are useful to your development! Please let us know if you have any feedback.  

Join the discussions

Endpoints for Shared Contacts

-resolved-

Search conversations: Unsupported search modifier provided

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 have any insight into why this might be happening or whether anything has recently changed with this endpoint?

Saving emails to 3rd party software via API

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

n8n + Front API: How to enforce the order of multiple attachments in a draft? (Also: how to work with message templates + predefined attachments?)

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 the remaining 3 customer-specific PDFs.Problem: There is no way to create a draft from a template via n8nI discovered that: Front templates can be created manually in the Front UI Front templates can be fetched via the API (GET /message_templates) But I could not find any endpoint that allows me to instantiate a template into a draft programmatically Unless I'm misunderstanding something, it appears that the Front API does not currently support creating a draft directly from an existing message template. Because of this, I must manually rebuild the draft body in n8n and manually attach all files instead of relying on the template’s built-in content and attachments.Since the template already provides 6 of the standard documents, being able to create a draft from that template via API would simplify the automation significantly.If Front does support template-based draft creation via API, I would appreciate guidance.Main Issue: Attachment order is not deterministicI have tried two attachment strategies:A) Upload all attachments in one PATCH request (multipart/form-data)Even though I send all attachments in the exact desired order, the final order shown in the Front UI is not consistent. Sometimes they appear reordered, but I cannot identify the sorting logic.B) Multiple PATCH calls — always resending the full listSince PATCH replaces attachments rather than appending, I attempted:PATCH 1 → attachments = [file1]PATCH 2 → attachments = [file1, file2]PATCH 3 → attachments = [file1, file2, file3]…PATCH 9 → full list of 9 in the desired orderEven with this method, Front sometimes displays attachments in a different order than the order sent to the API.What I need to know Does the Front API guarantee that attachment order will be preserved? If yes: In which order? The order they appear inside the multipart request? Or does Front reorder attachments internally? Is there a recommended method to reliably enforce attachment ordering? For example: adding filename prefixes such as 01_, 02_, etc. → It did not work for me Is there a supported way to instantiate a message template via the API? Since the template already contains 6 predefined attachments, being able to use it directly would make the automation far easier. If the API is not designed to maintain a fixed order, what does Front consider best practice for achieving predictable attachment ordering? Any clarification or recommendations would be greatly appreciated.

Plugin SDK with Retool / Google Sign In

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.openUrlInPopup", Front.openUrlInPopup)Front.openUrlInPopup("https://{mydomain}.retool.com/googlelogin", {  width: 600,  height: 800,})When I load that into the sidebar, the console.log runs (I toggled on the dev tools in Front) and I can see the Front.openUrlInPopup method showing just fine, but nothing happens/the function doesn’t run and no popup appears.I have already read everything in this thread: Look for a bit of guidance to help make this happen

Is GET /teammate_groups supposed to return an empty list?

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 listing endpoint? Any help would be appreciated.

Events calendar

Check back regularly for upcoming events

Leaderboard

Awarded badges

Show all badges

Need more help?

Terms & ConditionsCookie settingsAccessibility statement