Developers

Hi folks,I’m new to the Front API and am trying to understand how to use the two conversation date fields created_at and waiting_since. I recently pulled a conversation from Front in which there are four messages sent between 16:53:05 and 17:04:14 on March 28, 2022. As expected, waiting_since is equal to 1648487054, i.e., Mon Mar 28 2022 17:04:14 GMT+0000, which does correspond to the “oldest unreplied message”. But created_at has the value of 1706893362.369 – Fri Feb 02 2024 17:02:42 GMT+0000. That doesn’t make sense to me. Am I missing something? Is there a field that stores the true created_at value, or do we just need to pull the timestamp of the first message? Cheers,Matt

Hi all!We’ve built a sidebar plugin that serves up relevant information to our users about the email that they’re viewing.One of the things we’d like to do is allow them to download documents related to the email.We have an API that we’re reaching out to that returns the file in base-64. We’ve been unable to serve the file up to the user to download as the iframe the plugin is in doesn’t allow popups or downloads.We’ve considered temporarily saving the file to blob storage and then using the openUrl function to access it but that seems like an expensive solution.Any insight would be appreciated!

Hello Front Support. Can anybody answer my Questionhttps://stackoverflow.com/questions/78108047/frontapp-livechat-integration-in-android-webview-not-get-hide-as-per-guide

Hi, when creating a message, sometimes the error type: smpt_conn_error is returned. How can I solve this problem? Is it maybe something we can fix in Inbox settings?

Dynamic objects are now integrated with rules. This means that you can use Front’s powerful rule system to customize when and how dynamic objects apply to your workflows.  IMPORTANTRules have been auto-generated for all existing dynamic object configurations. These auto-generated rules have been named Create dynamic objects. While you are welcome to edit these rules, please note that disabling or deleting these rules will stop the associated dynamic objects from working.   Where to manage dynamic object rulesYou can manage existing dynamic object rules from Settings > Company name / Workspace name > Rules. As noted in the above callout, dynamic objects that you created prior to

I installed Front Chat on my website today, which is great so far, except that it’s exceptionally noisy in the developer console. It announces itself, it announces it’s using something called bugsnap, it spews out a load of SameSite and Partitioned cookie warnings, a few debugging messages from Ably, tells me about “frontChatChannelToken”.All of this makes real warnings a lot harder to see. What’s going on here? Can I switch off the non-cookie debug messages at all? Is there a “I’m in Production, WTF” flag I can switch on?

Hello, We have an active integration for pushing messages into Front and we are trying to wrap up a webhook to receive incoming messages from Front. We have a few questions. 1. The Authorization.Id that is coming through in the request doesn't mean anything to us at the moment. It’s not clear how this is created or where it comes from. We did see; however, that the Payload.Conversation.Assignee.Id is the same value we are already storing on our side when setting up the Integration to send messages. This looks like an easy way for us to identify who the message is for. Will this value always be populated when we're getting messages in the webhook or is it possible to get a message without an Assignee? 2. The attachment object in the payload does not contain any byte or steam data but it does have a URL. When we go to this URL we get a

Hello,We are currently building an integration with Front that will utilize Webhooks. In the “Verifying Integrity” portion of the setup on step 4 it states to “Apply the hmac SHA256 algorithm using the token provided during webhook configuration as the key [output in base 64].”Where do we get this token? The basic information tab only lists the App UID and App Secret while the OAuth tab only lists the Client ID and Client Secret. Are one of these to be used as the token or does it come from somewhere else.Second, it also says to use the raw request body. I was hoping to confirm what the expected value of the raw request body should look like. "{\"type\": \"sync\",\"authorization\": {\"id\": \"cmp_abc\"}}”or {\u0022type\u0022: \u0022sync\u0022,\u0022authorization\u0022: {\u0022id\u0022: \u0022cmp_abc\u0022}} Thanks!

You can now sort messages returned by the List conversation messages endpoint by their creation date.The endpoint now includes the query parameters sort_by and sort_order. Set sort_by to created_at, and then specify whether you want the sort_order to return messages as asc (oldest first) or desc (newest first) results.

Is there a way to automatically extract addresses (e.g. from signatures) for Accounts In Front? Rght now we do this by hand but its cumbersome. Thinking about extracting this via Chatgpt as a JSON and write it to the Account automatically…. Any ideas?

Hi,  I am debating utilizing the Zoom Plugin in Front to streamline the automation for my team. Due to the type of work that is common in our field I believe that there may be too many factors to add-on in our rules. Since all email’s received can have incorrect information, e.g. wrong date referenced, wrong start time, different start dates/times/locations listed on the attachment that is sent to us from what is mentioned in the body of the email. Is there a workaround that will forego these factors to all the ability to automate this in Front? Or does anyone have any ideas on suggestions? 

I am fetching “Reply Time (avg)” Metric from Core Front API on weekly basis.  The problem I'm encountering is that when there are no replies sent on a particular day, the reply time for that day is recorded as 0. However, when calculating the average weekly reply time, I don't want to include these 0 values if there are no replies on that day. How can I retrieve this metric accordingly?Because of 0s the “Reply Time (avg)” is getting significantly lowered.I'm open to alternative methodologies/approaches to address this issue. 

I am trying to use the frontapp API to get a url that directly links to the contact in frontapp. This url typically looks like "https://app.frontapp.com/contacts-manager/contacts/global/{{contact_identifier}}" When I use the API to retrieve the contact information, there is only one id field (starting with crd_), and it does not match the required contact_identifier needed for the url (which is a number) Can anyone tell me how to get the required contact_identifier? Or alternatively, is there a way to link to the contact page with the id from the API?

Hi,We've encountered an issue with the expiration of the refresh token. According to the documentation, refresh tokens are valid for 6 months.The documentation states:> Repeat this process as necessary, ensuring you use the refresh token at least once before its 6-month expiration to obtain a new set of credentials without having to restart the OAuth process from step one.However, when we use the `POST https://app.frontapp.com/oauth/token` endpoint to obtain a new pair of access and refresh tokens, we indeed receive a new valid access token (extended for 1 hour), but the refresh token remains unchanged, including its expiration.As a result, we are unable to update the refresh token. How can we resolve this issue?I am testing with the following refresh token:- Issued At: 1699617655 (11/10/2

Hi there,We just ingested raw Front data via Fivetran<> Front connector. However I’m struggling to reconcile the message “direction” - how is this determined?We want to use this data to track SLAs etc and monitor performance. We are also ingested the “analytics export” to get SLA specific data such as reply time.However, when I go to compare the two data sources (analytics export vs message data via Fivetran), I see that the message direction is sometimes different. Ie. in the analytics export it says its “inbound” whereas in the message data, it says “is_inbound” is false.This is confusing to me. Is it to do with cc.ing other members of the company? How come the two data methods don’t follow the same pattern?Would appreciate some insight on this! Thanks :)

Hi Front team. I want to bring my own custom, existing chatbot backend to Front. I don’t want to recreate my bot using Front bot tools. What would be the best and fastest approach to use a custom chatbot in Front? Do you have ideas on how to implement customer escalation from bot to human? My Front API doc reading suggests that using a custom channel to communicate the bot would work. What do you think of this approach?Thanks in advance. 

What’s the difference between “Avg Response Time” and “Avg Total Reply Time” ?  

Use case: I created a draft and I want to share it with my colleagues so they can edit it. They just have to click on this url and it opens the front webapp on a page where they can see and edit the draft / message. How do I create that url?

Hey,Is it possible when using the Create message reply endpoint to change the ‘from’ field?This is our use case:We receive an email from a client to a personal inbox We move it to a team inbox using Update conversation endpoint We reply to it using Create message reply endpointI’d like the ‘from’ address to be the one in the new inbox I moved the conversation to, but instead, the message is sent from the personal email that received the first message.How can I accomplish this?  Thanks!

Sometimes when creating a new conversation this error is returned, however it’s not always clear which resource presents an issue creating the conversation.Usually it’s a tag, and we have to investigate which tag doesn’t exist, although we’ve also had issues where the channel was re-added and presented a new channel ID. For debugging purposes, it’d be great if the ID of the resource not found was returned along with the error.

As the digital landscape continues to evolve, the role of social networking platforms in connecting individuals and professionals becomes increasingly significant. One platform that stands out in the professional networking sphere is LinkedIn. With its focus on career development, networking, and industry insights, LinkedIn has become a staple for professionals worldwide. This discussion stems from the intriguing possibility of leveraging LinkedIn as an additional connector within Front's App Store, offering new avenues for businesses to tap into diverse markets and streamline their recruitment processes. Let's consider a scenario: Imagine a startup business seeking to recruit young, talented software engineers for new graduate positions or summer internships. Typically, startups face challenges in sourcing candidates due to limited recruiting resources. One of their primary channels for sourcing candidates is LinkedIn, where they reach out to graduating

I do not see an option to extract the account from the context API? I try to go throught the conversation via context.conversation.recipient?.contact but I do not see the account anywhere. Is this not possible?Basically I want to extract both the conversations recipient and their respective account (if any) from the context Its quite urgent and any help is highly appreciated. 

Hello,I started getting this error out of blue today while sending an attachment via the messages endpoint:{"_error":{"status":400,"title":"Bad request","message":"Body did not satisfy requirements","details":["body.body: missing"]}} The code that I am using to send the message and attachment hasn’t been changed in months and was working since this morning. Any idea why this would start happening all of the sudden? This is the request that i am sending: POST: .....messagesContent-Type: multipart/form-data; boundary=----------------------------8dc226f5fd04b07Accept: application/jsonAuthorization: Bearer ****Host: api2.frontapp.comContent-Length: 99953Expect: 100-continueConnection: Keep-Alive------------------------------8dc226f5fd04b07Content-Disposition: form-data; name="subject";Test FRONT app integration---------------

When I try to connect a sidebar plugin to my localserver (e.g. http://localhost:5173/) I constantly get a cors issue from the front network:Request URL: http://localhost:5173/?auth_secret=ec16a8fd2f7765fcReferrer Policy: origin-when-cross-origin(blocked:other) I followed the exact tutorial using vite, then tried again with nextjs: Same error in both cases. What am I missing?  

Hey all,We thought we were utilizing all of Front’s features…. until today when we learned about dynamic objects - mind blown!  Since I am not a developer, we’re seeking any tips, tricks or help articles for how to configure a dynamic variable when the Target URL doesn’t include the “text pattern.” For example, I’d like to create a dynamic variable for our Order numbers, but our Salesforce link doesn’t actually ID the order number in the URL. Thanks for any advice!