Overview

Connectors provide a no-code means of making API calls to external systems and can also transform URLs or strings found in comments or messages into structured Orders, Shipments, Itineraries, Tasks, etc. that are easy to access right from a conversation in Front. With connectors, you can build rules and macros that retrieve or update information in external systems and also attach a summary of information from an external system directly to conversations in Front.

Connectors come in two varieties:

• Application requests—these connectors make API calls to external systems.
• Application objects—these connectors identify matching patterns (such as order IDs) in Front conversations or comments and automatically attach a structured object to the conversation that contains information about and a link to the external resource.

To learn how to add a connector feature to your app, refer to our Help Center articles.

Sample code for connectors

Refer to our Sample applications page for example code related to connectors.

Connectors Learning Path on the Front Academy

We created an in-depth tutorial for using Connectors, including building your own Connector with Asana, on the Front Academy.

Connector examples

Application requests

Application requests represent API requests. You can use application requests within rules, macros, and chatbot flows. For example, you might create an application request that cancels an order in your e-commerce or fulfilment system. Front users could then trigger that application within a macro, as shown in the following image.

You can use API requests to perform actions in other systems or retrieve data from them for use in Front workflows. You can imagine updating the status of different objects in external services or databases, creating a new object, retrieving data for use in rules, etc. So long as the system you're working with provides a public API, you can leverage the power of application requests to interact with that API without writing a single line of code.

Application objects

If a customer writes in to your team with a question that references a particular order, shipment, itinerary, task, etc., an application object can automatically extract that object’s URL and other metadata, and attach it to the header of the conversation for easy access:

This also applies to objects referenced in comments, which can also be easily previewed:

When attached to the conversation header, it’s easy to open the object in your external CRM/TMS/management system, or view details directly in Front:

Furthermore, application objects can do more than attach a link to a conversation. If you want more information at a glance, application objects can surface it to your Front users, as shown in the following image of an example Shopify order.