Solved

Hey if anyone knows how to fix this I would greatly appreciate the help! I’m trying to automate our client onboarding process to create a Front inbox for each client we have. In Zapier (that’s where all of our automation/apis/onboarding stuff is stored) I am doing an API Request (Beta) in Front trying to create the inbox. Below is a screenshot of how it’s currently set up: When I run this I get back the following:{"_error":{"status":400,"title":"Bad request","message":"Body did not satisfy requirements","details":["body.name: missing"]}}Can anyone help me get this error resolved so that it recognizes the name I’m trying to give it? Thanks so much!

We have teams from all over the world working but we want to keep responses to those individual time zones separate based on the team. How can we set up different working hours per team?

These integrations are great but could someone explain why the same phone number cannot be used for both SMS and Whatsapp through Twilio?

Hey, We have started using discussions for chat and office announcements. Is there an option to export discussions to a file? Sometimes we need to find an information in an older announcement but the search function doesn’t work as the history is not loaded. The only option is to scroll up but it takes a lot of time. Thanks, 

Is it feasible to retrieve the URL of a conversation within the FrontApp application through the API? Specifically, I am referring to the URL structure within the FrontApp application itself. It seems that the URL structure differs, and there are no apparent 'conversation' or 'message' IDs corresponding to what the API returns.For instance, in the case of a conversation in a shared inbox, the URL structure is as follows: 'https://app.frontapp.com/inboxes/teams/folders/{somenumbers}/unassigned/{somenumbers}'.

Hello:I was wondering which would be the best way to retrieve the important information in the body of a message through the API.Actually, I am retrieving all the messages from a conversation through the endPoint:https://api2.frontapp.com/conversations/{cnv_id}/messagesThen, I get the text of the message through the property:_results[x].textBut it gets to a point in the conversation where signatures and threads are included in the text property.Is this related to the way email clients deal with the emails? Or is there a better way to retrieve this information from the API?Thanks a lot for your time.My best regards.Juan.

I’m unable to understand the search filters regarding conversation status. The docs list a number of status to filter on here using the “is” field name https://dev.frontapp.com/docs/search-1, but they’re not explained, and they’re not mutually exclusive. A convo can’t be “assigned” AND “unassigned” but it can be “assigned” AND “open”?In this community answer the solution url ishttps://api2.frontapp.com/conversations/search/is:assigned%20is:openwhich works for me. The comment talks about “open” serving to filter archived convos, but this isn’t explained. But if I remove “is:open” from my own searches, the “assigned” status is ignored; everything is returned. ie this returns convos with status: archived:https://api2.frontapp.com/conversations/search/is:assigned%20is:openif I replace “open” with “unreplied”, I also get every status message. Can you help me understand how all the “is” options work? Thanks! Also, minor thing, the docs have a bug - https://dev.frontapp.com/reference/search-c

Hi,We have set up two rules for automatic receipt confirmations. These worked without any problems until yesterday. Now the message no longer goes out via email, but it still works on WhatsApp. When I look at the time of the last rule application, both show December 14th. 17:**. I can't find any reason why the rule no longer works today. Can you help me there?

Is there a way to hide any of the announcement popups, placeholder graphics, and maybe even all the front jokes? They’re just big, repetitive, and unnecessary for our team. It gets really old. 

All of our teammates (including agents that do not have admin access) have used the team inboxes dropdown menu every week for the past several months (some of us have used that feature even longer than this). We use the analytics feature weekly and everyone reports their own analytics per inbox. Each of our agents have always been able to do this regardless of whether or not they had admin access. However, since last week, they have no longer been able to filter their personal analytics by inbox/channel. Has this happened to anyone else?

Hi! My company has a use case to list conversations in a specific inbox that have been created since a specific, dynamic, timestamp. Ex: we want to list all new conversations in an inbox that have been created within the last 30 minutes.  So far, we’ve been attempting to use the list conversations endpoint, and newly created search endpoint, without success. Each time, it seems the Front API is returning a much larger timeframe of conversations within the inbox.  Here’s the API request we’re currently using: https://api2.frontapp.com/conversations/search/inbox:XYZ after:1694445506?limit=100 Has anyone had success here? Would love to hear if there’s a better way!

 I’m working on setting up an automation between Front and Clio (law firm management software that my firm uses), and have to use the Front API through Zapier’s API Request Beta. I currently have a Company Rule in Front that triggers off of adding a tag to a conversation and then sends a POST to a Zapier webhook. I’m trying to then pull conversation fields via the below API GET request, but an receiving the error seen in the below screenshot. I’m adept with Zapier and have used it with Front previously, but unfortunately the specific process automation I’m building requires use of the API and I’m admittedly not super familiar with dealing with those requests. Any suggestions to get the GET request pinging the conversations end point working? 

Does anyone have any general tips with front use so we can compare to see how we might do better? Thanks. 

Hi, We have had some issues with tagging emails correctly due to the wide variety of how someone can request an action from us. What is the best way to get around or deal with this? It’s been mentioned that set email formats/forms would work well.  Thanks, 

Is there any possibility to fetch the messages (not conversation) which has respond time more than 48 hours (example). The purpose of this to fetch the messages respond which has breached pre-defined SLAs (which in our case is 48 hours). So, what I am thinking is to fetch number of messages sent in a specific time period and then fetch the messages with respond time more than 48 hours. The below code (API Endpoint) can be used to fetch number of messages sent: import requestsurl = "https://api2.frontapp.com/analytics/reports"payload = { "metrics": ["num_messages_sent"] }headers = {    "accept": "application/json",    "content-type": "application/json",    "authorization": "Bearer <Token>"}response = requests.post(url, json=payload, headers=headers)print(response.text) But how can I fetch messages with respond time more than 48 hours ?If there is better approach to perform same task, feel free to mention ? 

I have templates that are important and will be used, however, rarely used. Is there a feature to hide or archive message templates?

Hello. I have a problem with our emails to ONE specific domain.Our user sends emails from a shared inbox with a Google group channel.SOMETIMES there is an error in Front, and the email to NAME@DOMAIN.cz is not delivered. The error in Front looks like: bounce / 450 4.1.8 <bounces+7887486-433e-NAME=DOMAIN.cz@front-mail.OURDOMAIN.com>: Sender address rejected: Domain not found. There is no incoming email with info about rejected emails.Most of the time, user’s emails to this address go uninterrupted. Their admin can see only this log entry when the email is rejected:Sender address rejected: Domain not found; from=<bounces+7887486-433e-NAME=DOMAIN.cz@front-mail.OURDOMAIN.com> to=<NAME@DOMAIN.cz> proto=ESMTP helo=<o6.front-mail.frontapp.com> I have no info about their email server.Deliverability in Front is set correctly. As far as I know, there are no similar problems with other domains. What should I or their admin set up to make an uninterrupted flow of emails?

Hi! When someone sends me an email with an .ics file attached, Front shows the the event above the email message with a calendar icon. But as far as I can see, there is no way to have Front add the event to my calendar. Do I have to do it manually? 

When do “Launched” Ideas become 'Already Available?'I received an email from Front, regarding the status of an Idea that had its status changed to ‘Launched.’ (See Below)  The status ‘Launched’ does not appear in the list of “what each idea status means.”When do “Launched” ideas become available in our Front instance?  Do we have access to a calendar of upcoming releases?  it would be helpful to know in advance of new features going live, so that Administrators could become familiar with them and appropriate training be made available/created for end users.  

Paginating over the events API is broken:I’m using the “list events” API. My first request is to https://api2.frontapp.com/events The response contains some events + _pagination.next = https://relayapp.api.frontapp.com/events?page_token=Token_1 When I use the next page URL, I get the following response: The exact same events as in my first request (I was expecting the next batch of events) As _pagination.next, I receive the exact same URL I’ve just requested (with page_token=Token_1) This makes this API unusable, since I don’t have a way to paginate and iterate over events.Note:This happens both with and without a query. So it can’t be a query issue on my side. Also this only happens in /events, but pagination works as expected for any other API (e.g. conversations). However, only /events is jumping from the api2.frontapp.com domain to my app-specific domain in pagination, so might be related to that?Is there a known bug on your side?Thanks!Luis.

I am working to try and improve search functionality for my teammates. One of the continuous complaints is that some of our group reporting crowds our search results when looking for previous conversations. We tag these reports which allows us to archive them and keep our inbox clean, but if you search using the order number then all of those reports appear in the search. When trying to filter these out I do not see an inverse filter, as in filter by tags that do not equal “Reports”. Anyone had any luck with inverse filtering? 

Hi, I’m receiving a error saying “Draft Failure Mail Server rejected a command”. Can you help me please? 

I’d like to use the Core API to generate draft messages. In the docs, I notice that there are examples for use in JavaScript (including fetch and XHR APIs). When I tested this code in the browser console, the request was rejected due to cross-origin headers (specifically the requesting origin was not allowed by Access-Control-Allowed-Origins). Is calling the API from the browser supported? And if so, how would I go about configuring CORS headers?Thanks!

Instead of calling Webhook URL without any authentication , can Front consume an API with Basic Authentication and send the Event payload real-time rule based ?

Hi everyone!I’m just playing around with Front, as it has most of the features I am looking for.However, I am quite puzzled about why there is no way to import history from custom SMTP -adresses.I understand that it might be difficult to support this against all the different service providers out there. But shouldn’t it at least be possible to import a PST -file from Outlook?Does anyone know if they plan to add it? Or any other smart way of importing a file like this?Thanks in advance!