Developers

We are excited to announce the release of sample code that demonstrates how to augment dynamic objects with information fetched from a server or API. The code also demonstrates how to verify that requests to the server are coming from Front.  We hope this code is useful and results in more powerful dynamic object use cases for customers!

The Fetch an analytics export endpoint now enforces a maximum of 5,120,000 events or messages within a single export. If your export exceeds this number, the API will return a response with the status parameter set to too_big. To address this scenario, reduce the time period of the export and fetch it again.

I would like to know if I can have front to authenticate a user against a front plugin. The plugin does receive an auth_secret but it is a global value and can easily be traced in the http inspector.Is there an option to have an auth_secret per user that only that user can see?How secure is the `tea_XXXX` id I can find in `context.teammate.id`. I think that these don’t seem to be not visible / guessable on the front end?Basically, how sure can I be that in the context that my plugin receives, the teammate is actually the currently logged in front teammate and that the context has not been tampered with? Thanks,Tilmann

Between Sunday 2023-11-19 0800 UTC and Sunday 2023-11-19 0900 UTC, customers in our us-west-1 data center region may experience an interruption to loading conversations, loading conversation lists, and reopening conversations from an integration. This is due to planned maintenance work required on a core database service. What is the impact?During the window, the conversations viewing experience will be degraded or unavailable. The display of new messages, counter updates of all workspaces, and some asynchronous conversation mass-actions will be delayed. Developers trying to use the API via integrations may receive a 503 "service unavailable" error in their list conversations responses during the interruption. This should be resolved once the maintenance is complete. Why are we doing this?One of our core database clusters needs to be restarted during the maintenance window while we perform an important security upgrade. We are doing this type of work during off-hours to minimize disrup

Based on rules and also the option to, for example, return the conversation stages as a 'tag' so that they are also visible, or as a view in Front.

I'm working on an integration project. In the initial phase of this integration, I aim to create a web application with a webhook feature. This allows clients to integrate the application into their front-end. When specific events occur, the requests will be forwarded to the application configured in the webhook.I'm seeking a method to distinguish which client is sending the request. Specifically, I'm exploring the possibility of configuring multiple API keys or OAuth tokens (one for each client) that can be included in the request payload.

Currently I’m adding webhook via Rules.I wanted to handle permanent deletion of conversation as well as merging conversations.However I don’t see any trigger in rules for merging.And after adding trigger “Conversation is deleted” it seems that event is not coming.Am I doing something wrong?

Between Sunday 2023-11-12 0200 UTC and Sunday 2023-11-12 0300 UTC, customers in our eu-west-1 data center region may experience an interruption to loading conversations, loading conversation lists, and reopening conversations from an integration. This is due to planned maintenance work required on a core database service. What is the impact?During the window, the conversations viewing experience will be degraded or unavailable. The display of new messages, counter updates of all workspaces, and some asynchronous conversation mass-actions will be delayed. Developers trying to use the API via integrations may receive a 503 "service unavailable" error in their list conversations responses during the interruption. This should be resolved once the maintenance is complete. Why are we doing this?One of our core database clusters needs to be restarted during the maintenance window while we perform an important security upgrade. We are doing this type of work during off-hours to minimize disrup

We now offer a sample application that demonstrates how to export conversations and messages from Front! The application demonstrates: Listing all inboxes Searching for conversations Applying filters to the conversation search Handling pagination of results from the Core API Export all conversations with messages and attachments included Applying rate limit handlers Check out the application and GitHub source code on our Developer Portal.

Are you guys considering an integration with Playvox?  They are the Work force management partners for dialpad.  https://www.playvox.com/integrations/

My organization receives communication in multiple forms , Email / voicemail etc . I was wondering if there was any way to combine or flag communications coming from the same person even if the message itself is not exactly the same?

Can't download my FCA cert, website is buggy, the overlay on the academy site prevents downloading and sharing:   

Is it possible to build User to User chat with Front? Or is it only for customer support? 

Regularly when typing compound words like doesnt and couldnt I leave out the apostrophe.  When I’m reviewing my email before sending, it is underlined in red.  In most applications, when I right click, it offers the most likely suggestion.  In front’s case, it does not.  It suggested “couldn’t’ve” and did not suggest “couldn’t”.  Not sure what spellcheck API y’all are using or if it’s something y’all developed, but the suggestions are not ideal.  While typing this I accidentally typed “msot” instead of “most” and it did not offer “most” as a suggestion.  My suggestion is to update the spellcheck suggestions.

Hello,We are moving Front messages to our data warehouse using FiveTran, we are experiencing error while fetching the data via API. I initially contacted FiveTran, but they told me the error is coming from Front side and contact you guys.  Below is the error message. {"_error": {"message": "Plan exceeded.","status": 403,"title": "Forbidden","type": "resource_unavailable"}}

I’m trying to use the Add conversation link endpoint but after every attempt with various conversation ids I am getting from the UI, I get a 404 error:{"_error":{"status":404,"title":"Not found","message":"Invalid id"}}I’ve confirmed I’m using valid conversation ids because the Get conversation endpoint works fine with the same ids.Below is an example curl request I’m performing, generated and copied from the docs:Any ideas what could be going on?curl --request POST \ --url https://api2.frontapp.com/conversations/cnv_14lrv1os/links \ --header 'authorization: Bearer XXXXXXXXXX' \ --header 'content-type: application/json' \ --data '{ "link_ids": [ "Example Link" ], "link_external_urls": [ "https://www.example.com" ]} 

Heya. Some of our customers are using the Front App to read our html emails, however we’ve received some complaints about email formatting. It looks like our paragraph <p> tags are not being treat the same as in for eg Gmail, specifically the padding/spacing between tags.Front:vs Gmail:Our raw html looks like this <p>We just wanted to drop you a note to say thank you for your recent order.</p> <p>We’ve been building ___ for almost 30 years now, relying on personal recommendations and word of mouth to grow organically and slowly, rather than on flashy advertising with big budgets we don’t have.</p> <p>We never want to forget that our business relies on people like you choosing to buy from us, and of course telling their friends :-)</p>Could i get some advice on what styling Front expects to have the same expected behaviour as Gmail? I do not see any info on the developer docs about email display issues Regards

Now we are using Twilio/Front integration as our WhatsApp channel. Is there a reason to switch to direct Front/WhatsApp integration? 

We are using Authorize.net for billing.Is there a way to integrate Front with Authorize.net?

This morning a bunch of users started having messages fail with “Send Later: This message will be sent in 1 minute” then “Failed to send. Message temporarily rejected by mail server.” Frontstatus implies everything’s OK; downdetector tells me GMail’s OK. I don’t know what the issue is or what to do about it.Do you?Regards,Brian

I was recently asked how to automatically transition a Front Chat conversation into an email thread. While there’s not currently a way to do this natively in Front, using a rule and basic Zap allows you to build a quick automation to turn a chat conversation into an email thread. There’s plenty that could be improved about this approach, but I hope it serves as a good template for building an automation like this.  The JS code from the Zapier Code step shown in the screencast is:try {  // Fetch the contact info  const res = await fetch(inputData.contactUrl, {    headers: { Authorization: 'Bearer YOUR_API_TOKEN' }  });  const contact = await res.json();  const emailHandle = contact.handles.find((h) => h.source === 'email').handle  if (!emailHandle) {    return {error: {message: "No email handle found"}}  }    return {email: emailHandle}} catch (error) {  return { error };} 

Custom Fields in the Core APIThe Core API now exposes endpoints to list the custom fields that can be used on different resources:Use GET /accounts/custom_fields to list the custom fields available on an Account (docs). Use GET /contacts/custom_fields to list the custom fields available on a Contact (docs).Use GET /conversations/custom_fields to list the custom fields available on a Conversation (docs). Use GET /inboxes/custom_fields  to list the custom fields available on an Inbox (docs). Use GET /teammates/custom_fields  to list the custom fields available on a Teammate (docs). In addition, the Custom Field data model now returns all the supported values for the Custom Field of type enum. Accessing email messages in the .eml formatThe Get message (GET /messages/:message_id) endpoint now supports customizing the response's Content Type.By default, the endpoint returns the documented JSON data. However, you can now request the response to contain the message in the .eml format by setti

I’m successfully creating new conversations by posting `/inboxes/inb_1234/imported_messages` endpont.  it returns something like:{ conversation_reference: '...', message_uid: 'abcdefg88fbc88046053ecd6e319', status: 'accepted' } I want the conversation id from that so I can add links etc.   So I’m passing the message_uid to messages as so:curl --request GET \ --url https://api2.frontapp.com/messages/alt:uid:abcdefg88fbc88046053ecd6e319 \ --header 'accept: application/json' \ --header 'authorization: Bearer <token>but that returns: { "_error": { "status": 404, "title": "Not found" }} What am I doing wrong?

My sidebar plugin has some interactions that invoke confirmations via `window.confirm()`, e.g. deleting a line item pops up “Are you sure?” type messages.These currently don’t work when viewing app in Front’s iframe sidebar, and I believe it’s because the “allow-modals” permission is not set on the iFrame sandbox.Can this be added?

Between Sunday 2023-10-22 0700 UTC and Sunday 2023-10-22 0800 UTC, customers in our us-west-2 data center region may experience an interruption to loading conversations, loading conversation lists, and reopening conversations from an integration. This is due to planned maintenance work required on a core database service. What is the impact?During the window, the conversations viewing experience will be degraded or unavailable. The display of new messages, counter updates of all workspaces, and some asynchronous conversation mass-actions will be delayed. Developers trying to use the API via integrations may receive a 503 "service unavailable" error in their list conversations responses during the interruption. This should be resolved once the maintenance is complete. Why are we doing this?One of our core database clusters needs to be restarted during the maintenance window while we perform an important security upgrade. We are doing this type of work during off-hours to minimize disrup