Developers

 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? 

UPDATE: There’s a new version of the MCP server. Please join the following group to learn how to get started: https://community.front.com/groups/beta-mcp-server-83The data access note for the original MCP server does not apply to the new one linked above. We're excited to announce the beta release of the Front MCP server — and we'd love for you to try it.Model Context Protocol (MCP) is an open standard that lets AI applications securely connect to external data sources and tools. With the Front MCP server, AI-powered tools like Claude, Cursor, Windsurf, and others can interact directly with your Front account and API documentation using natural language — no manual API calls required.What does that look like in practice?Ask your AI assistant to pull open conversations from a specific inbox, then tag or triage them Query your Front account data in real time to inform what you're building Explore Front's API endpoints and get full details about specific ones — without digging through doc

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!

At Front we’re constantly looking for ways to improve our product, and direct feedback from customers is one of the key influences on our product roadmap. The ideas portal below is the best way to share product feedback with our product team. Guidelines for submitting Ideas:Be sure to search for similar ideas that have already been posted. This helps to avoid duplicates and will save you time from typing out a new Idea. You can comment on an existing Idea to add additional details that would be helpful for our team to consider. Be as detailed as possible: when describing your idea, please provide as much detail as possible, including example use cases and why the feature would be valuable to you. This helps our product team better understand the potential impact of your idea. Submit one idea at a time: this makes it easier for our product team to review and track the progress of each idea.  When you first submit an idea, it may take some time before the idea is made visible for others

Sharing a quick snippet showing how you can install Front Chat as a React component. This example was specifically tested using Next.js 13 with the /app directory.First, create a FrontChat component. We’re using the Next Script component.Have the onLoad prop call an ‘init’ function for our widget, which just runs the content of the chat JS snippet provided in your Chat channel settings.// @/components/front-chat.tsx"use client";import Script from "next/script";export function FrontChat() { return ( <Script id="front-chat-script" src="https://chat-assets.frontapp.com/v1/chat.bundle.js" onLoad={initFrontChat} ></Script> );}function initFrontChat() { //@ts-expect-error window.FrontChat("init", { chatId: "YOUR_FRONT_CHAT_ID", useDefaultLauncher: true, });}(If anyone can tell me how to get rid of the TS error on window.FrontChat, I’d love to hear it!)To use the FrontChat component, it’s probably best to insert it into your layout.tsx, just before

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

We Are trying to implement a Plugin using the Google Sign Button. The problem is however that the sign does not work because Google is trying to open a new window. That of course doesn't work in the plug-in within the Front app.  Hence, my question is if anyone else has built such an integration and how did they manage to integrate Google sign in within the Front app plugin?

On September 1st 2024, we will be introducing E.164 phone number normalization to the Front API to address issues caused by inconsistent phone number handles attached to contacts. Phone number handles for contacts in Front can be created via the API, the Front contacts manager, incoming messages in channels, CRM contact syncs, and CSV import of contacts. With so many different ways of creating contacts and storing phone numbers for those contacts, it’s important to normalize the data because the different input formats can lead to duplicate contacts and related search issues. To prepare for this change, make sure your API requests (including those made through the Zapier integration) are sending valid phone numbers with the country code included. Country codes must be preceded by a plus (+) sign. Read the “Potential impacts” section below for details.If you experience any issues with phone number normalization, reach out to us and we can roll the feature back for your company instance

Important update: Google will continue to support third-party cookies. It is still important to provide alternatives to third-party cookies for those users who do not consent to the use of third-party cookies, as noted in the rest of this article. However, Google continuing to support third-party cookies allows you to continue using these cookies in Front plugins if you have control over the browser decisions of your users (if all your plugin users belong to your company, for example). There is no longer a planned deprecation. The rest of this topic is left for historical context, but please note it is outdated.********************************************************************************************************** In a significant move towards enhancing user privacy, major web browsers are on a trajectory to deprecate support for third-party cookies to limit cross-site tracking. This shift has notable implications for developers of Front custom plugins or third-party integrations tha

Two questions:1.-Ive completed the walk through for the Highway intergration. The issue i have is there are many different ways carriers, cusotmers, fastors, etc….use  MC. EXAMPLES: MC#123435, MC# 12345, MC12345, MC 123345, MC: 123445. Im catching very few MC’s because of this, Am i missing something?  I could create seperate objects, but that would consume a ton of time. (a copy or ability to use dyamic objects for other links, or an OR statement)  2.- Fraud detector, im getting multiple comments in conversations at times, i understood that the custom senders object was supposed to stop that part. Any help would be great.   

We are happy to announce that you can now access knowledge base API endpoints through the Core API. These endpoints allow you to read and update your internal and external Front knowledge bases. With the API, you now have the flexibility to process your knowledge base content for various purposes, including advanced display on different websites and additional means of importing content. Read the docs on our Developer Portal to start using the knowledge base API endpoints.

We are making a breaking change to the Create a new analytics export endpoint offered by our Core API. The endpoint will now require you to specify the columns that will be present in the export. Previously, the endpoint generated an export that included all available columns. In addition, three columns will be deprecated from the export: Resolution time, Replies to resolve, and Final resolution. You should use Total reply time, Replies to resolution, and Stage resolution time instead. Why are we making these changes?We are making these changes for the following reasons:By explicitly specifying the columns you need in the export, future additions to the available columns will not affect your export. This ensures backwards compatibility as we continue to enrich the Analytics data.  Customers who need a subset of columns in their exports can benefit from faster exports and smaller response sizes. The Resolution time, Replies to resolve, and Final resolution columns are being deprecated b

We used the “Create Draft Reply” https://dev.frontapp.com/reference/post_conversations-conversation-id-draftsIn the API, it requires a channel_id which is only optional when we simply reply the conversation https://dev.frontapp.com/reference/post_conversations-conversation-id-messages Where should I get the channel_id? I want to make sure the channel_id is the same as the inbound message that I creating draft for. I looked through both the conversation and message entity, there is no channel_id.

Hi all, Not sure if this is the correct location for this. I run a Technical Support team and we have inbound via email and WhatsApp as well as Zoho CRM tasks.  Zoho Desk didn’t work out for us as it would not work with custom modules of CRM. We don’t a yet have a developer.  Front looks like it may suit us but we use personal email, shared team inboxes and we also use WhatsApp groups that involve the team but also customers in those groups. Can Front work with WhatsApp groups (as well as 1 to 1 WhatsApps) and Zoho tasks?

Sharing a quick snippet of how to build a Front Application Webhook handler in Make.com. This differs a little from handling a simple webhook call from a Front rule, as you need to perform a setup step and have your webhook respond to a challenge sent by Front’s webhook server. To start, head to Make.com and create a new Scenario with a Webhooks (Custom webhook) trigger. Click the Create a webhook button, and open up the advanced settings. Be sure to enable Get request headers; these are required in the next step. Hit Save. Creating a Webhook trigger in Make.com Next, we can add a Flow Control > Router step. We’ll use this to branch into two different paths, depending on whether this is the initial setup challenge webhook call, or receiving regular webhook updates.For our challenge path, we’ll configure a filter that looks like this:Make.com Router, filtering on request headersWhat this does is access the HTTP headers of the webhook request, and extracts the one header with the name

Hello. I am looking for suggestions, tried sales and sent a support ticket, but there is no reply. I would like to set up my clients as individual, siloed TEAMS. They would have full access to the other users on their team (all 50 users at a salon), 100 users on another team at an insurance company, and 5 people on another team at a dance studio for example. The idea is that the Salon would have about 50 people doing scheduling, having a shared inbox, individual google business emails etc. They could use Front, well, like Front.  But, today, when I started to set them up, I noticed a user in 1 team can see ALL of the other members of every other team, this does not seem right to me.  In fact, my client noticed it before I did and was like why do I see this person and that person, who are those people? I want to add them to MY account so I can get stuff pushed to me from them that I need to take care of, and they can share messages and chat with each other and me but NOT the insurance c

I would love to know if/when NLP and LLMs will be available for dynamic object extraction. Currently the feature is pretty limited by the user providing an exact match, which isn’t great for a white glove customer experience.

Our operations team would like to take advantage of Events data and I’m working on interpreting the API documentation.The documentation says: Lists all the detailed events which occured (sic) in the inboxes of the company ordered in reverse chronological order (newest first).But we are given the following query param:q stringSearch query object with optional properties before, after, or types. before and after should be a timestamp in seconds with up to 3 decimal places. types should be a list of event types. I did some digging and discovered how the Search Query Object is defined, kind of. Looks like we can search using the before: and after: available here, but this appears to only index on conversations created_at, created before/after the supplied parameter. Given that this is an event endpoint, I find this behavior confusing. Surely multiple events can occur after a conversation is created. Is the proposed way of interacting with this endpoint to:1. run a backfill, or at least for

Going forward, Front will disable application webhooks that do not respond successfully. After three failed attempts, the webhook will be disabled and Front will stop sending events to your URL. We expect this change will mostly impact webhooks set up during development that are no longer used. However, if an active webhook experiences downtime and is disabled, you can go to the Webhook feature of your developer app and click Update to re-verify and re-enable it.