Developers

You can now download attachments via the following resource-specific endpoints:Download attachment for a comment Download attachment for a message template Download attachment for a messageThe ability to download message template attachments is a new benefit. The other benefit of these endpoints is that Front validates that the requester has access to the resource in question versus only validating the attachment access credentials. Fetch attachments via their download URLFront recommends you fetch attachments via their download URL (which includes resource-specific routing) versus providing only the ID to the generic Download attachment endpoint. 

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.

You can now access entry point data in the Plugin SDK to learn how a Front user opened your plugin. A new property called entryPoint is now available in the context object. Read the full details on our Developer Portal This property allows you to handle different scenarios depending on where the plugin was opened. The current plugin entry points are:SIDEBAR—User opened a plugin in the Front sidebar. COMPOSER_TOOLBAR—User opened a plugin in the composer toolbar while composing a message. CONTACT_HANDLE—User opened a plugin from a Front contact’s phone handle. More information on plugins that open from this entry point in order to make or handle calls will be coming soon!

I understand that Teammate Groups is a relatively new feature, which might explain why it’s not available in the API yet, but I was wondering when/if we might gain access to those groups of Front users that we define and use for managing Inbox access, etc. (found in the app under Settings > Company > Teammate groups).So far, references to “teammate groups” in the API documentation seem to reference contact groups owned by a team member, which is not what I’m looking for.Perhaps this question is also related to Front’s SCIM functionality–is there any documentation related to that functionality?

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.

The Plugin SDK now offers the delegateNewWindowsToFront utility function. This function allows you to capture link events that open in a new window and handle them through Front. This function replaces the deprecated delegateAnchorClicksToFront function.

You can now use token instrospection to specify an application channel’s name and address.Token introspection is an additional step in the OAuth2 flow where the client sends a request to the external server to retrieve information about the provided access token. This request allows Front to obtain details of the channel from the external service. Read more on our Developer Portal!

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!

Looking for a developer to assist in building a custom pipedrive plugin. The existing one is limited in terms of functionality, we’d like to create one that allows us to create a proper deal/opportunity with more information/fields. Please comment contact details/info so i can reach out :)

The Update conversation endpoint now correctly updates conversation statuses in personal inboxes. Before the update, the status update would only be applied at the team-level. The status update did not affect private conversations or propagate to the conversation assignee.From now on, the conversation status update will follow the behavior of our rule engine: the status update will be applied to the conversation assignee and owners for private conversations in addition to the shared inbox at the workspace level. This update will gradually be released to all customers over the next week. Please comment below if you want to access it immediately. PS: The update only impacts the conversation status for assignee and private conversation owners. It does not impact the status of the conversation for its followers (participants who are not the assignee or owner of the private conversation).

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?   

The documentation mentions that React is not needed, but there aren’t any examples of subscribing to context events without using React, so I’m hoping you can point me in the right direction.Is there a simple way to use the sdk without React for sidebar plugins? Preferably, a way to include a script directly on a page (without a build step) and then subscribe to events.Something similar to this would be great:<script type="text/javascript" src="https://dl.frontapp.com/libs/frontjs.min.js"></script><script>Front.contextUpdates.subscribe(context => { switch(context.type) { case 'noConversation': console.log('No conversation selected'); break; case 'singleConversation': console.log('Selected conversation:', context.conversation); break; case 'multiConversations': console.log('Multiple conversations selected', context.conversations); break; default: console.error(`Unsupported context type: ${context.type}`); break;

Hi, we setup the webhook to receive inbound events. We also have rules on Front to tag each conversation based on its channel. The rules work well on tagging.However, we have some hiccups on the webhook. In the ideal case, once there is a new conversation, the rule tags the message, our webhook receive the inbound events about the message and the event comes with tag list, so we can route it to proper processors. However, we sometimes receive the inbound events with empty tag lists, therefore I cannot do the proper routing for the next step. It appears the tagging happened after Front server send out the event to our webhook.Anybody knows how to fix this?

Hello, I am assessing whether Front will work for my business use case. I need to use a number of Twilio WhatsApp channels for my clients all of which are Business accounts. Business accounts have some limitations around messaging and messaging windows and as a result need to use pre-cleared message templates when sending messages to users outside of a conversation window. Does Front support sending Twilio message templates via the Front API?Additionally does Front support web hooks for listening to messages (both inbound and outbound messages to the channels?Thanks!

I am looking to setup on Front to allow agents to view conversations happening in WhatsApp Business accounts that I manage as well as handle quick questions with my API so that agents do not need to handle those types of questions. I have already added the channel but am confused as to how to send messages to users via Front or if I should be sending messages via the Twilio SDK and Front will just sync with Twilio through the channel. Usually platforms like Front have a webhook that I have to plugin to my WhatsApp sender in twilio but that documentation/requirement does not seem to be present for Front? 

I am looking to retrieve the First Reply Time for messages via the Analytics API. Maybe I am missing something, but this doesn’t seem to be available in the .csv downloaded. Is there a way to pull this metric via the API?

I created a Telegram bot, linked to my inboxes, and I’m developping a custom integration to send advanced Telegram messages, how can I get the chat_id of this conversation (Telegram-one), so my integrated plugin can retreive it on the current/opened conversation?I managed to get the @username, I have my Telegram bot tokens, but no way to get the chat_id.

I want to send an email using the frontapp api. When the recipient of that email reply to that email, I want him to send that reply email to someone else. How to I set that Reply-to property when I create an email in front? This is the email header I want to set a value for: https://www.getresponse.com/help/reply-to-field.html

Love all the new chatbot features - but when using chatbot a message is automatically hovering over the chat widget - is there a way not to have that and only have the chatbot start when a user actually opens the chat? It is quite annoying for customers to have a big bubble showing if they have no intention of chatting.  

We want our application to be used as public. That's why we filled out your form and sent it, but we haven't received a response from you for a long time. https://app.frontapp.com/oauth/authorizeWe do not want to receive this warning during authorize. We would be happy if you could help us.