Developer Q&A

I’m trying to use ‘strict-dynamic’ for my ‘script-src’ content security policy.I have a nonce set up in my page where I include the Front chat widget script: <script nonce="random nonce here" type="text/javascript" src='https://chat-assets.frontapp.com/v1/chat.bundle.js'></script>but it appears that that chat.bundle.js script dynamically loads app.bundle.js, which leads to a CSP violation in Chrome:Refused to load the script 'https://chat-assets.frontapp.com/v1/app.bundle.js?v=840fb872' because it violates the following Content Security Policy directive: "script-src 'self' 'strict-dynamic' chat-assets.frontapp.com 'nonce-9a6157311c94f2a96914fe5ac561d6fc'". Note that 'strict-dynamic' is present, so host-based allowlisting is disabled. Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.Is there a way to use strict-dynamic with the Front chat widget?

How do I lookup a front email using exchange or office365 message-id?

Is it possible to get a conversation’s updated_at datetime from the Plugin SDK?

Hey, We had previously added a few links to contacts in our Front instance. However, we wish to remove them now. The API explains how that can be done with lists, but doesn’t really go into contact links. How can we achieve this?

If we setup OAuth with a agent, but later, the agent resigned and her account deactivated, will this affect the OAuth?

Is it possible to get Ticket data from the context (singleConversation) via the plugin SDK?

We are looking for a report, that will provide the below information to export so that we can merge with our inbound phone traffic. DateHourInboxDirection

Is there a way to preview a message attachment from the Sidebar plugin, for example using the plugin SDK downloadAttachment()?I am currently only getting a File object returned from Front.downloadAttachment('msg_xxx', 'fil_xxx') with the following properties:lastModified:  1740416909060lastModifiedDate:  Mon Feb 24 2025 18:08:29 GMT+0100 (Central European Standard Time) {}name: "fd880b5930634b94bfa961a2b3815db2.jpg"size:  293622type:  "image/jpeg"webkitRelativePath: ""

A few questions regarding teammates:What would be a scenario where multiple teammates are returned by listTeammates()? Is the current front user always the first user in the array? Is there a better way of identifying the current front user from the plugin, ie. where only the current user is returned?

Hello!I wonder why “Get message seen status” https://dev.frontapp.com/reference/get-message-seen-status API works only for outbound messages? Wasn't the initial idea to have a info WHEN a teammate has seen INBOUND message?{    "status": 400,    "title": "Bad request",    "message": "You cannot see seen status for an inbound message."}Why am I asking this? We’re implementing the Frontapp plugin which gonna track the time when a teammate seen a inbound message from a customer (to measure activity of diff(seen,archived)). There’re not those fields in the webhook triggers, so we can’t receive the time of “seen” activities. The plugin context API doesn’t have this data too.Also I see the internal CONVERSATION by ID request that returns the “seen” data for it. I think it can be useful for our task, but this data is not in the conversation PUBLIC API. Could you cover 2 questions please:1. How to get “seen” information per teammate for a MESSAGE?2. If for some reason (1) is not possible, how c

We have been integrating Front Chat into our app, and the experience has been great so far. However, we are facing a challenge with supporting multiple logins on the same machine.Expected Behavior:• When a user logs in, they should see the continuation of their own previous chat (if available).• If a different user logs in, they should only see their own chat history (or start a new conversation if no prior chat exists).Current Issue:Right now, when a new user logs in on the same machine, they see the chat history of the first logged-in user, which we want to avoid.We attempted using the shutdown() method from the Front Chat SDK to clear the chat on logout, but this also removes the previous chat history, preventing the original user from retrieving their past conversations when they log back in.can someone help me out on this matter? 

Hey all,I am trying to build a connection to Front to interact with the conversations, so we can assign the assignees to the conversations through the API. Using the example of the API documentation keeps giving me errors and I can’t figure out what is going wrong. I’m using the Update conversation assignee with the NodeJS example, but I keep getting an error:{"_error":{"status":400,"title":"Bad request","message":"Body did not satisfy requirements","details":["body.assignee_id: missing"]}}I’ve tried it with JSON and FormData, but the error stays the same, my latest example code is the following const frontUpdateAssignee = async ({ conversation, assignee, token }) => {   const options = {    method: "PUT",    headers: {      accept: "multipart/form-data",      authorization: `Bearer ${token}`,    },    body: JSON.stringify({ assignee_id: "tea_hjdlj" }),  };  const updateAssignee = await fetch(    `https://api2.frontapp.com/conversations/${conversation}/assignee`,    options  )    .t

Using fetchPath() I can retrieve the current conversation URL, but the function returns a Promise Object.How do I get the “PromiseResult” value from the object, ie. how do I get the path into a string?Front.contextUpdates.subscribe(context => { let path = context.fetchPath();}); 

Hi,We are currently integrating the chat SDK into our apps, and while reviewing the documentation, we came across the Identify Users page.We have a few questions regarding the use of userId for identification, as we do not have user phone numbers in all cases and were hoping to use userId instead of email.Specifically, we would like clarification on the following: What is the userId? Is it an ID that we define within our system, or is it the contact ID generated by Front? Behavior when using a custom userId: If the userId is defined by us, will Front create a new contact when it encounters the userId for the first time, regardless of the email or phone provided in the contact object? If so, how can we prevent the creation of duplicate contacts? We already have a large number of contacts in Front and want to avoid duplication. Behavior when userId is defined by Front: If the userId is generated by Front, will it simply add the email and phone provided in the contact object to the e

 I have integrated the Chat Widget code in my iOS app. It was working very good.But today I noticed suddenly getting error in RED “Not delivered - connection issues” I have noticed the first message is delivered successfully but after that always getting the mentioned error.When I tried to run the code in my browser it shows AxiosError. What could be the reason?Here is my latest code<html> <body> <script src="https://chat.frontapp.com/v1/chat.bundle.js"></script> <script> function initChat(name, userId, userHash) { window.FrontChat('init', { chatId: 'ce4c58cd0f7cbcd3ed3eaf3b0b0XXXX', useDefaultLauncher: true, shouldShowWindowOnLaunch: false, shouldMobileReloadOnClose: true, name: name, userHash: userHash, userId: userId, onInitCompleted: () => {

Hello, I’m looking to build a plugin for Front. The concern I have is about security. The recommended pattern to use token verification is embed the “secret” in the search param rather than a header.Is there a way to embed the token in the header of the request instead so that it’s not obvious from the url?https://dev.frontapp.com/docs/security#token-verification

We have developed a custom app for Front to display insights, and we would like to store the app's configuration directly within the app settings for ease of access and management. Could you please guide us on the following points:Is it possible to store custom configuration data within the app settings in Front? If yes, what is the recommended approach or API to achieve this? Are there any limitations or best practices we should consider while implementing this functionality?Your assistance would be greatly appreciated, as it will help us optimize our app and ensure a seamless user experience.Looking forward to your guidance.

Our Front workflow involves generating emails and scheduling their sends on a daily basis. Our current flow is:Generate the email text and attachments programmatically. The email content includes a blurb about the time the email should be scheduled (roughly based on the local time of the recipient) Send a POST to `/drafts` with the email content and attachments On success, open the link to the draft Manually schedule the send according the the email content’s scheduled send blurb, and delete the blurb in the email.The only manual part of this flow is that we need to manually schedule the send (and delete the blurb saying the send time, but that’s a byproduct), which is a hassle. I haven’t been able to find a way to programmatically schedule sending via the API but that would allow us to do this whole flow programmatically. It doesn’t look like there’s anything in the Messages or Drafts APIs. Does this functionality exist? If not, I’m curious why and if it might ever be on the roadmap.

Is it possible to separate comments, whether from an original comments or from two merged conversations?

I face a very weird situation when trying to convert the message.created_at to the timestamp. Firstly, my understanding is that the date type for the created_at is float. Is that correct? So the number is the seconds passed since epic, and fraction is the millisconds. Did I understand it correctly? Then I used the following code to turn it into Java Date object.new java.util.Date(TimeUnit.SECONDS.toMillis((long)last_message.created_at.floatValue()))Then I used the following code to transform the Date into stringnew SimpleDateFormat("yyyy-MM-dd hh:mm:ss.SSS"); There are two things weird:(1) I have two messages, sent in absolutely different time, 20 - 30 seconds apart. But somehow the output of timestamp is exactly the same.(2) For afternoon 1pm, instead showing 13:xx:xx, it shows 01:xx:xx.

We are facing a problem whenever the client disable the app fro app store from as shown in attachment. And then when reenable that app and then try to obtain oauth (access token) via api using existing refresh token within the period of 6 months i.e still refresh token is valid, api provide response {"error":"invalid_grant","error_description":"Invalid refresh token"} 

I have a few questions about the chat widget:Is it possible to swap out the current icon for one of our own? Is it possible to have customize the icon and have the ability to show/hide, move the chat bubble around or only show it on specific pages?Thank you!

Team is receiving a draft failure error when trying to send emails?Only one of my gmail channels is having this issue, other gmail channels are not having this. And this channel is working fine on its own. I can send emails in this gmail but in Front I can’t. 

Hey everyone, I'm working on setting up an Application Channel to connect to my backend for sending and receiving messages. I'm trying to understand the setup(using the template to help understand), but it feels like the guide leaves out some key details. Here are a few questions I have:When configuring the Channel Type in my app, what exactly is the difference between ‘Contact Types’ (Email, Phone, Custom)? When adding the channel to my workspace, it asks for a token. What value should this be for the template to work correctly?   This might relate to question 2, but every time I add the new channel, I immediately get an error that says, “Our access to this account was revoked. New messages will not be imported until you reauthorize,” with a “Reauthorize” button. Clicking it doesn’t trigger anything on the server side, and I’m not seeing any issues in the console logs I added. Any ideas on how to resolve this?   Excited to make Front a core tool for our team!

I am unable to add a Channel as the app states I have reached my limit, but in the attached image you will observe that I have no Channels. What am I doing wrong?