What we do
Tools
Industries
Department
How we workLet's talk →
Home/Front/Front Integrations for Data Your Team Looks Up
Front

Front Integrations for the Record Your Teammates Keep Opening in Another Tab

A customer replies to a shared inbox thread asking whether their refund went through, and whoever picks it up opens Stripe, then the order system, then comes back to Front to write two lines. Front offers several ways to close that loop. An App Store app is the answer when one exists for your tool. A Connector suits a rule or macro that only needs to look something up or post a change. A sidebar plugin is for records teammates need to work with, and an application channel is for messages that come from somewhere Front doesn't already support.

Front integration routes, matched to the job

What you need Route in Front Limits to know
Your CRM record (Salesforce, HubSpot) beside the conversation An app from the Front App Store Covers the standard objects and actions. Custom fields or objects your team depends on may not appear.
A rule or macro that looks up an order or posts a status to another system A Connector application request, set up by an admin without code Usable in rules, macros and chatbot flows. A slow external system can run past Front's timeout, and Front documents a webhook-based pattern for that case.
Order or ticket numbers in messages turned into links to the record Connector application objects Front's help center lists custom application objects on the Professional plan or above.
Teammates acting on a record from the sidebar, with buttons A sidebar plugin built with the Plugin SDK It's a web app you host, calling your own backend. It's the most flexible route and the most work to build.
Messages from a portal, app or messaging tool Front has no channel for An application channel built on the Channel API Legacy custom channels are in maintenance mode, and their outbound messages don't thread into the same conversation.
Simple hand-offs, such as posting a new conversation to a sheet Zapier, or a Front rule calling a webhook Fine for one-way steps. Anything that needs to come back into the conversation outgrows it.

Front apps that look connected but leave the tab open

The app shows the record but nothing can be changed

How you'll know: Teammates can read the order in the sidebar, then still open the other system to issue the refund or update the address.

Fix: Add the action where the other system's API allows it, through a Connector request for a single change or a plugin for anything with more than one step.

Records matched by email address only

How you'll know: A message from a shared address like accounts@ shows the wrong customer, or none.

Fix: Match on something in the message instead, such as an order or account number, using application objects or a plugin that reads the conversation.

A custom channel whose replies start new conversations

How you'll know: Messages from your portal arrive, but a teammate's reply sits apart from the thread it answers.

Fix: Rebuild it as an application channel on the Channel API, which Front recommends and which threads both directions.

A Connector call that stalls on a slow system

How you'll know: The rule runs, and the lookup or update never arrives for some conversations.

Fix: Move the slow work behind a webhook and post the result back into Front when it's ready, rather than waiting inside the rule.

Front integration builds n-frames takes on

01

Customer context from a system with no Front app

Order history, account status or billing details from an in-house or industry system, shown in a sidebar plugin the moment a teammate opens the conversation.

A second tab for every reply.The record beside the message.
02

Conversations that change things elsewhere

A tag, an assignment or an archived conversation in Front updates a record, opens a task or notifies another system, through Front's webhooks or a Connector.

Someone copies the outcome over by hand.The other system updates when the conversation does.
03

A new channel into the shared inbox

Messages from a customer portal, a marketplace or a messaging tool arrive in Front as real conversations, with replies sent back the same way, built as an application channel.

Portal messages forwarded as email.Two-way conversations in Front.
04

An App Store app extended where it stops

When the installed app covers the standard fields but not yours, n-frames adds the missing lookup or action alongside it instead of replacing what already works.

Front App Store, Connector and plugin questions

Who can build a Front integration for a system with no App Store app?

That's the work n-frames takes on: sidebar plugins on Front's Plugin SDK that show records from an in-house or industry system, Connector requests that let a rule look something up or post a change, and application channels on the Channel API for messages from a portal or app. Scoping starts from the lookup your teammates repeat most.

What does Front integrate with?

Front's App Store lists apps for tools such as Salesforce, HubSpot, Slack, Jira and Shopify, and Front connects to Zapier. Beyond the listed apps, Connectors, sidebar plugins, the Channel API and the Core API with webhooks let you reach almost any system that has an API of its own.

Which tools does Front already integrate with natively?

The ones in its App Store, which you install from Front's settings without writing code. If your tool isn't listed, a Connector is the next thing to try, since an admin can set one up against the tool's API without a developer.

Can Front show order or account data inside a conversation?

Yes, two ways. Application objects turn an order or account number in a message into a link to the record, and a sidebar plugin can show the full record, with actions, next to the conversation. Both need the other system to have an API Front can call.

Front works for us, but agents still check another tab for context. Is that worth fixing?

If it happens on most replies, it is. A few seconds per lookup across a team answering all day adds up to hours a week, and lookups done in a hurry are where wrong answers come from. A plugin or Connector for that one system is usually a contained piece of work.

What's the difference between a custom channel and an application channel in Front?

Custom channels are the older route and are in maintenance mode: they can receive messages, but replies sent out don't thread into the same conversation. Application channels use the Channel API, sync both directions and can be kept private to your company or published in the App Store.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.