API news & updates

We've revamped the Connectors Academy course to reflect all the recent improvements to the no-code framework—and this time, you'll build something you can actually use right away.The updated course walks you through building a Connector with Asana that lets teammates create a new task in Asana directly from Front. Along the way, you'll learn how to:Chain multiple app requests together to pull in workspaces, projects, and tasks from Asana Build dynamic dropdown menus that let teammates select the right project, task, or any other context—adaptable to any use case, like selecting the correct order for a customer! Use pagination and other new Connector features recently added to the platform Arrange complex logic visually in the flow builder, including using app request nodes to perform external actions without writing that logic inside a dynamic variableHead o

 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

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

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!

We are thrilled to feature recent community contributions to our sample code! Read on to learn what sample apps and code your peers have recently shared with the community. MCP serverMany thanks to ​@zqush for going above and beyond to provide an example of a Model Context Protocol (MCP) server for Front! An MCP server is a standardized way to connect AI models to external data sources and tools, enabling them to access real-time information and perform tasks securely.  PHP code snippetsThank you ​@jross for contributing PHP versions of common Front code snippets!

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:

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:

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.  

We are thrilled to announce the implementation of a new rate limiting system that offers a more sophisticated and user-friendly approach to managing API requests. We will start rolling this new rate limiter out on Monday, September 22nd, with the aim of updating all companies by Friday, September 26th. Our improved rate limiter provides the following key enhancements: 1. Removing the penalty for 429 rate-limited requestsIn the past, hitting the rate limit meant that requests that returned a 429 response informing you of the breach also counted against your limit, which could result in compounding and unnecessarily long windows before your limit was reset. With the new system, 429 rate-limited requests will not count towards your rate limit, making it clearer to understand when your new rate limit window will replenish.2. Burst Limit for Occasional Traffic SpikesThe introduction of a burst limit provides

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

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!

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