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.