Developer discussion

I built a custom integration between Front and Atlassian Statuspages. This allows you to more easily associate support cases with incidents posted on your status site.  How does it work?The app subscribe to incidents from an Atlassian Statuspage via the webhooks feature, and gets notified immediately on any new incidents. That event triggers an Application Object to be created in Front with the incident data. You can configure the App Object to match any cases where link to that incident is mentioned in a message or comment, to automatically apply the App Object to the conversation. On receiving further updates via the webhook about the incident status, you can use Application Triggers to update the status of the App Object. Once the incident moves to a Resolved state, add a rule to automatically re-open each linked conversation so your team can quickly respond and let customers know the incident has been resolved.  Given that you can’t authenticate or format the structure of Statuspag

Hello,  We are looking for a developer who could connect Front to our property management software with API and Webhooks. We could also use some additional settings in Front, if you are interested send us a message or an e-mail on info@rent4me.hr I hope this is in line with the community guidelines. Kind regards,

Hello,We are looking for a developer to help us migrate 6000 email conversation as well as 10 inboxes (and some tags and contacts) over to a different Front account. We have been using Front for a year through a third-party company that we pay to perform customer service duties, but we now want to do this in-house and are looking to open our own account.

It appears like Model Context Protocol (MCP) is the protocol that everyone is moving towards as it puts the burden of keeping everything “tidy” on the service provider rather than the client.  There are already many official MCP servers available and more on the way. There are also community developed ones. Is anyone else exploring this?Cheers!

Hello,Sharing how to send an API request using PHP Curl and Bearer token:<?phpdefine('FRONT_API_KEY', 'xxxxxxxxxxxxxxxxxxxxxxxxxxx');/** * Performs an API call using cURL * * @since 1.0.0 * * @global string FRONT_API_KEY * * @param string $url URL. * @param string $requestType 'GET', 'PUT', 'PATCH', etc. * @param array $postFields Array of fields and values to be posted to URL * * @return array Associated array of JSON objects returned from API call. * */function api_call($url, $requestType, $postFields) { try { $ch = curl_init(); if ($ch === false) { throw new Exception("Failed to initialize"); } curl_setopt($ch, CURLOPT_URL, $url); curl_setopt($ch, CURLOPT_CUSTOMREQUEST, $requestType); if (isset($postFields)) { $json = json_encode($postFields); curl_setopt($ch, CURLOPT_POSTFIELDS, $json); } curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); curl_setopt($ch, CURLOPT_USERAGENT, "curl/7.7

Hello,Working on my Front Admin certification and this is my contribution to the community. I haven’t seen many PHP integrations and wanted to share how I am verifying the Front signature.<?phpdefine('FRONT_WEBHOOK_API_KEY', 'xxxxxxxxxxxxxxxxxxxxx');/** * Verify Front rule webhook request function * * Calculates the base64 encoded HMAC hash of the request body (payload) using SHA1 algorithm and the Front API key. * Compares the hash to the X-Front-Signature header to verify the request is from Front. * * @since 1.0.0 * * @param string $payload Request body. * * @return bool true if verified, otherwise false. * * @link https://dev.frontapp.com/docs/webhooks-1#configure-rule-webhooks */function is_valid_front_webhook($payload){ if (isset($_SERVER['HTTP_X_FRONT_SIGNATURE'])) { $hexHash = hash_hmac('sha1', $payload, mb_convert_encoding(FRONT_WEBHOOK_API_KEY, 'UTF-8')); $base64Hash = base64_encode(hex2bin($hexHash)); return hash_equals($_SERVER['HTTP_X_FRONT_SI

If your team has SLA agreements you can’t afford to miss, or you already page on-call teammates for urgent issues, you might want to consider automating this using Front Rules and Application Requests.This post will guide you through how to add a Front Application Request to trigger a PagerDuty incident, and how to enable that from a Rule in Front. 1. Create a PagerDuty ServiceThe PagerDuty Service is required as the “entry point” for creating the incident. When creating the PagerDuty Service, select the Events API V2 integration;Creating a PagerDuty Service2. Create your Front Application RequestHead into Front > Settings > Developers, and create a new App. Give it a useful name like “PagerDuty”. Click into the Servers tab in your new App, and create a server. The PagerDuty events API is hosted at https://events.pagerduty.com, so we can add that as the Server Origin value. No auth is needed here - this is specified elsewhere.Click Save. 3.  Add Application RequestClick into the

Does anyone have any insight or tips to share regarding using the Front API in PowerApps via PowerAutomate?  I've been considering exploring this possibility. 

I put together a simple TypeScript template app to reliably handle incoming Application Webhook events. It can be deployed to Railway in a couple of clicks.Where can I try it?You can install the template here → Front.com Application Webhook ReceiverHow does it work?At a high level, there’s an exposed API endpoint which you register with Front as the destination for for your webhook events.On receipt, various security and validity checks are performed, the event is added to a background processing queue, and the app quickly responds to Front, acknowledging successful receipt. You then have a secondary process monitoring the queue, which is where you add your logic to save the events to your own data store, or performing your custom business logic to handle them.What tech is used?This is a template which can be deployed on Railway in a couple of clicks. The API router and middleware is powered by Hono - a fast, lightweight web framework.The background job queue uses BullMQ, built on Redi

I’ll be working on NetSuite > Front.Just starting up the post, here!

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?

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 :)

Hi Front Community! A lot of times you might need to request a full (or multiple) inbox export from Front Support. These exports follow the following file structure:Inboxes → Inbox → Conversation → Messages.csvThe export format provided can make it challenging to get a clear overview of all messages within an inbox. This is a common issue for teams that frequently conduct inbox audits to review messages for analytics or other purposes.To address this, I’ve developed a Python script that consolidates all messages.csv files from Front Support inbox exports into a single consolidated Messages CSV file for each inbox:import osimport csv'''This is for a multiple inbox export.Please note if the exports are quite large you should consider chunking output CSVs. This is because applications like Excel have a row limit on CSVs that is just over 1 million.Expected file structure is:Inboxes -> Inbox folder -> Conversation folder -> Messages.csv'''# Path to the Inboxes folderparent_folder_

I think it would be a marvelous idea to Integrate a google transaltor plugin into Front.  Who else agrees?

If i want to tag or archive conversations that happened in the past, I would like to be able to trigger a rule manually that can do that.  

I think the developer documentation under your “Guides” section needs to include a page on how to link to messages and conversations in the Front web app.I went to the high level “Guides” section hoping to find information on this, and couldn’t, so had to turn to Google and found two related conversations in these forums from other users who had the same question:In both instances, there were confusing responses from the Front team that the links returned from the API under the _links property could be used to link to the Front app, however this is not the case. You need to construct the URL yourself with https://app.frontapp.com/open/{message_or_convseration_id}Here is the relevant API Reference pages for conversations and messages: https://dev.frontapp.com/reference/conversations#opening-a-conversation-in-fronthttps://dev.frontapp.com/reference/messages#opening-a-message-in-frontI think there could be either a new page under Guides / Fundamentals that discusses this, or at least addi

I see a google drive and Dropbox plugin. Is there an idea to also develop a plugin for SharePoint / OneDrive. Where you can easily select documents to share them with a client or directly upload files from mails into SharePoint?

I used to receive email notification of changes to the API functionality.I recently found that the maximum limit parameter for an event fetch has been reduced from 100 eventsto 15 events, but I had not received an email relating to this.Do such changes still get announced to an email distribution ?

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? 

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 students to explore potential o

Spinning up this thread to discuss all things related to implementing and maintaining a Highway dynamic object.

During Frontlines 2023 it was mentioned that the ability to link separate email threads together would be coming soon.  How soon will that feature be coming?  We typically have 2 email threads for every shipment and this will definitely save us some time! I am using Dynamics to get there now, but I can only imagine the ease of use this will add! 

I put together a screencast showing how you can build a Dynamic Object (with no-code) which can fetch order data from your Shopify account. It was built from scratch in ~10 minutes. Let me know what you think!