Developers

We've added a set of Time Off API endpoints to help you build integrations that stay in sync with teammate availability in Front. What is Time Off?A time off represents a scheduled out-of-office period for a teammate in Front. While active, the teammate's status switches to Out of office and any configured auto-responder starts replying to inbound messages on their behalf. When the period ends, their status returns to Available automatically. What you can buildThe Time Off API lets you read and manage these scheduled periods programmatically. A few example use cases:Surface upcoming absences in a workforce management tool Sync time off data with your HRIS Skip unavailable teammates when routing work from an external systemEndpointsGet time off List teammate time offs List team time offs Create time off Update time off Delete time offFor full reference docs, check out our Developer Portal.For an end-user overview of how time off works in Front, see Time off in the Help Center. Happy cod

We have a use case where we have a unique id, e.g. 12345, for each customer case and we want to have a unique email address with that id, e.g. 12345@cases.example.com, that a customer can send emails to when they have queries. We have setup the inbound flow so customers can send us emails to the unique email address and we can see them in the Front inbox, however, we can’t seem to be able to specify we are replying from that unique email address or set the reply to header to be that unique email address. This breaks our workflow. Is there any way around this?

Hi all, I’m struggling with something….I have a conversation custom field “Shipment Number” and an app object which is basically just a URL.I want to append the shipment number to the URL. Then I can create rules to populate this object when Shipment number is filled in.Is this possible?

Hi friends!I am implementing a custom solution and need to be able to search and identify contacts on Front with their phone number.I have tried https://api2.frontapp.com/contacts/alt:phone:[Number] returns an exact result if the number exists. However in many cases the number doesn’t exist and it return a 404 error which causes the custom template I am building to crash.I have also tried https://api2.frontapp.com/contacts?q=[Number] but the problem is that the query is ignored and all the contacts we have are returned every time and these contacts have no connection to the query. This is really not helpful. If this endpoint can return only contacts that have the query as a handle or name, that will be a lot more helpful.Has anyone had a reason to do something similar or is there anything I must have missed with searching contacts with the query method?

 If you've been looking to bring voice calling into Front, we just made it a lot easier to get started. We've published a voice channel template on GitHub that gives you a working foundation for building a full voice application channel integration — without starting from scratch.What the template coversAuthorizing Front users connecting to your channel via OAuth Instantiating a new channel and handling the webhook lifecycle Processing call status events (ringing, connected, hold, transferred, hangup, and more) Syncing call assets — transcripts, recordings, and summaries — back into Front conversations Displaying incoming call notifications to teammates via a sidebar plugin and managing the call lifecycle from thereThe template is built in TypeScript with Node and Express, but the architecture is straightforward enough to adapt to your language of choice.Getting startedThe repo includes a quickstart README if you want to get the code running before diving into the details, and a full t

You can now run sidebar plugins in the background by enabling the Run in background setting when you configure a plugin feature in your developer app. While this setting currently only supports voice channels through the new displayNotification and dismissNotification Plugin SDK functions, please leave us a comment about other use cases you’d like us to support so that our Product team can prioritize! Happy coding!

I’ve made a private oauth app to access resources. Only shared resources. I’ve limited the resource permissions to a pretty vanilla degree. However, whenever someone in my company tries to authorize the app, if they are not an admin then they cannot proceed.Is this expected, or am I doing it wrong? 

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 over to the course to access the new example, or view the full learning path if you’re new to Connectors.

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, 0, 0, 0)account_ids=['acc_xxxxx']start_ts = int(start_dt.timestamp())end_ts = int(end_dt.timestamp())body = { "start": int(start_ts), "end": int(end_ts), "timezone": "UTC", "filters": { "account_ids":

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? 

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 organizationCheck out the full Views API documentation to get started, or learn more about how views work in Front in our Help Center.

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 resources Delete – Remove resources Send – Create and send messages that start new conversations or reply to active ones (note: importing historical messages only requires Write permission) Best Practices✅ Limit permissions to only what your integration needs to prevent misuse or security issues✅ Check the Core API reference document

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 conversation"