Developer Q&A

From reading the documentation, it seems clear that the Context API can create new email drafts thought context.createDraft, I can get this to work in a very neat way. However, is this all that the Context API can do when it comes to creating new drafts?I see no info on creating a new internal discussion (https://explain.helloretail.com/xQuRABAe) or comment in a thread via the Context API. Which seems like something that should fit inside the scope of the current context? Instead I have found that the Core API does have the endpoint for creating comments and drafts (emails). However, I still can’t find any info of creating a new internal discussion draft? It also seems like a little bit of a workaround to use the Context API to create a new email draft, Core API to create a new comment. Did I get this right or have I missed something here?  

Hi, I’m currently working on a plugin that converts email messages to PDFs. To be able to do so, I need to know which messages are currently being selected by the user. However, there does not seem to be a way to list currently selected messages in Front’s context API, and to my knowledge we can only retrieve ALL of the messages inside a selected conversation using listMessages. I would really appreciate if someone could give me pointers on this. Thank you 😄.

Hello, I’m setting up provisioning in JumpCloud, and I must enter SCIM details for Front manually.  I’ve made an auto-provisioning token, but I still cannot connect to the SCIM server.  My gut feeling is that the SCIM server has a different base URL than https://api2.frontapp.com, but I’m not sure because I can’t find any documentation. Thanks in advance for any help,Brodie 

Hello,I need to know if I can connect Front to the Mulesoft application.The goal is to automatically send 100% of the documents received in Front, regardless of the channel, to Mulesoft, so that we can then read them and connect them to our Home Made CRM (possible from Mulesoft)Outlook can receive the mails, and send them to Mulesoft, but:I don't use Outlook of course Front receives a lot of What's App too, that's why the sending has to be done between Front and Mulesoft directlyThanks for your help! Jérémie

Hello all!I am finding that the plugin sdk does not allow for CRUD operations on front contacts. Is this correct? If this functionality is not available I am assuming I need to work with the core API.Is there a javascript library to work with the core api?

I am noticing that the is_spammer field is not returned from calls to GET contacts/{contact_id}.I am trying to add the ability to mark as spammer the contact from a plugin.Im using a php backend and the response body does not include the is_spammer field.Is there something I am doing wrong?

I’m working on a plugin which needs to list and parse messages and discussions using context.listMessages() and context.listComments()I ever receive the whole conversation, only the first 20 discussion messages and in the case of emails 3, even though the conversations contains many more.If I understand the docs correctly, I should use the nextPageToken form the response, in order to read more/all messages. I did this according to the documentation (see code below) This however, makes no difference and I still receive 3 or fewer emails.   const listAllEmails = async () => { const emailList = await context.listMessages(); let nextPageToken = emailList.token; const emails = emailList.results; while (nextPageToken) { const { results, token } = await context.listMessages(nextPageToken); nextPageToken = token; emails.push(...r

Hello,I am new to development and was wondering if anyone has made a SDK to connects Front to Hubspot?Ideally, we would want to make a plug in that would give us more options when creating a deal in Hubspot from the sidebar of Front.Any assistance on how to get started? Our first thought was Retool

Hi,I’m building a plugin to save a message’s attachment and send it directly to a Google Drive. The problem I’m facing is that the context.downloadAttachment() function is returning a broken file: // attachments state contains message_id and attachment_id of all the conversation's attachments const handleAttachmentDownload = (index) => { context.downloadAttachment( attachments[index].messageData.id, attachments[index].attachmentData.id ) .then((resp) => { console.log(resp) setPreview(URL.createObjectURL(resp)) }); };The promise is successfully returning a File but as we try to handle the file (previewing or sending it to a google drive it for example

Might be a big of a long shot, but I was wondering if it’s possible / what it would take to mimic the behavior of the Linear.app integration of linking a Front ticket to a Linear issue. I examined the requests that are sent when linking an issue from Front, and it seems there are a fair few things that are required to make that happen. Is there any way to trigger that programmatically? Or can anyone help with the steps required to replicate that behavior? Thanks for any help!

I’m attempting to get conversations for the last day and see that the “List Conversations” returns conversations sorted by most recent first. But there’s no great way of validating recency. I’ve resorted to pulling all messages for each conversation and checking to see that at least 1 message was created within the last day.Seeing as the List Conversations endpoint is doing some sort of server-side sorting with an updated_at property, is it possible to expose that so I can key off of it at as well? This would also be helpful when searching conversations too.Or if there’s some other way of getting this information please let me know. Thanks in advance!

Hello; In an effort to not miss clients contacting salespeople who have departed our company, I am modifying my offboarding script to add the user’s email to an ‘inactive’ inbox that only managers have access to.  I can successfully convert the Google user into a group and add it to the inbox, but if the user had their email set up in Front I get a “duplicate channel” error and have to go into the UI to manually delete the user and their private inbox.  Is there a way to manage this offboarding flow outside of the the UI? 

Is there a way to fetch/list only intercom conversations using the conversation api ?

Hello,I would like to know if when refreshing an access token (point 4. here : https://dev.frontapp.com/docs/oauth), the previous token is disabled even if his 1 hour lifetime is still ongoing, so there is only one token that is being replaced each time we do a refresh call to your API?Or the previous token is still valid till the end of his 1 hour lifetime ?Thank you in advance for your answer.

We would like to start measuring our shared inbox usage compliance, and we want to get insights from an analytics standpoint (volume for instance). We want to look into the ratio of messages one sends (either through Shared Inboxes or Individual Inboxes).

I am working on using the Front API to get some data we need into our BI Tool to analyze it, but I have a few questions. Basically, I need to get from the API the same data I get if I go to Analytics and get a Message Export. I wasn’t quite able to exactly that in the API so I just need a little direction on where to find it.We will also need the export to contain messages from personal inboxes. 

We are currently in the process of building an integration with Front. For our use case, we found the `List Events` API here, to be suitable. We want to only list archive events in a certain time window, and for that, we have tried using the `q` parameter, as mentioned in the document, but it doesn't seem to work, the response always contains all the events, irrespective of the query we use. Attaching a few curls we have tried curl --request GET      --url 'https://api2.frontapp.com/events?q=types%3Aarchive'      --header 'Accept: application/json'      --header 'Authorization: Bearer TOKEN'curl --request GET      --url 'https://api2.frontapp.com/events?q=after%3A1651470943.000'      --header 'Accept: application/j

We utilize our own plugin integration to pull customer data on each inbound data for our sales reps to see.We capture the customer's email address using "emailaddress = context.conversation.recipient.handle;"This is working fine except for our contact forms on our sites. These all send and are properly signed from noreply@domain.com. So we are unable to lookup the customer email in our system... The customer email is set in the reply-to field of the email. Our plugin works as expected as soon as the sales rep hits reply - the front conversation recipient changes at that point to the 'reply-to' address.How can we pull the reply-to address in our plugin from the initial load before hitting the reply button??

We could not find raw data about the CSAT but only percentages. We need to recover the data of our customers in a raw format… We are used to working in that way with other CRM solutions.We need the same with front. Do you have some guideline or examples as how to recover CSAT raw data?

Hi, I am trying to use Front's api to send a reply to a conversation, but am receiving the error "body did not satisfy requirements" I am using webhooks via Zapier to POST to the API. I've included the text below of the inputs- I tried to match everything as closely as possible to Front's documentation. Could you provide any advice into troubleshooting this error? URLhttps://api2.frontapp.com/conversations/cnv_12345/messagesPayload TypejsonDatato"person@example.com"options{"archive": true}signature_id"sig_12345"sender_name"Dale"channel_id"cha_12345"body"test"subject"test message"Wrap Request In ArrayfalseFileUnflattentrueBasic AuthHeadersAcceptapplication/jsonAuthorizationBearer xxxxxxxxxContent-Typeapplication/json

We've been running into an issue implementing the event sync from Front. While the webhook is working correctly, the alternative sync we wrote using the Events API seems not to respect the after filter in queries. When we make a request to e.g. https://companyDomain.api.frontapp.com/events?q=after:1652647350.45151, rather than getting only very recent events (that was basically the current UTC timestamp when I made the request) we get a paginated response with hundreds of thousands of results. Is this a bug on the Front end, or is there a different syntax we should use to query events after a certain time?

We’re hoping to send calendar invites through Front messages. Historically we’ve included the calendar invite as inline to the message using the multipart/alternative property where the invite renders as part of the message, but not sure this is available through the Front API.

Currently we have a rule for our team that when triggered sends an auto reply to the sender. We have changed something about our setup where this rule is no longer working properly.  I am hoping to get some assistanceHere is the specific use case: "A client requests a quote, the php backend sends an email to one of our addresses with the requested quote details. A front rule is triggered to send an auto-reply to the reply to address." Up until now the server for our website has been using phpmailer to send to one our emails, and it sets the replyTo email to the email we want to respond to.  The rule is triggered, the auto reply is sent, and it includes the body of the original message in the auto reply. I am told this all works fine.  But we are currently making a change to our system and may have to move away from using phpmailer. I have been testing using the front API to send the initial message. My problem is that I c

Hey there!Im working on a system in which I want to be able to reply to a conversation in Front, and immediately after, have it archive.Looking at the docs at https://dev.frontapp.com/reference/post_conversations-conversation-id-messages, I should be able to get that functionality by passing "options": { "archive": true }, however it doesn't seem to be working that way.Is there anything I'm doing wrong? Or is there a bug here?Im hitting the endpoint athttps://myDomain.api.frontapp.com/conversations/cnv_12345/messagesWith a json body of { "sender_name": "System - +123456789", "body": "Uhhh S

Attachments don't seem to be coming through. Any advice on what might be happening? What datatypes are typically accepted? Right now I'm using data:application/octet-stream