Connectors

If you’ve been using Connectors or are curious about incorporating them into your Front workflows, we’re looking to partner closely with a few customers to help you adopt them or take your existing usage to the next level. We’d also like to hear about what improvements we could make. Interested? Become one of our design partners: 

Connectors allow you to supercharge your macros with dropdown menus powered by API results. This means that Front teammates can select from a dynamic list of items populated from an external service, such as contacts from a CRM or goods from an inventory management system.  When your teammates open the dropdown menu in the macro to select the item they want to view or update in the macro, they might be confronted with a long list of results, making it hard to find the correct item. To solve this, add search and pagination parameters to your app requests. Search parameters allow teammates to search only for the items they’re interested in, filtering down the total results. Pagination parameters automatically add scrolling to the list, pulling in more results as your teammates your mouse down reviewing results. Vide

What we covered: We walked through how to build a Connector that lets your teammates update Salesforce objects—like opportunities, cases, and contacts—directly from Front conversations, no code required. Resources:Workshop Recording (starts at 3:50) - Watch the session to learn how to set up your Salesforce Connector in just 10-15 minutes  

Join Front’s community team for three hands-on Connectors workshops in January! Follow along as we automate workflows between Front and your 3rd-party tools. January 15: Salesforce <> Front workflows: Use Connectors to update Salesforce objects directly from your inbox. January 22: HubSpot <> Front workflows: Use Connectors to easily manage customer data in HubSpot. January 29: Jira <> Front workflows: Use Connectors to create Jira tickets from Front with just a few clicks. Register nowCan’t make it? No p

We recently launched a detailed video explaining how to set up a macro leveraging Connectors to process Stripe refunds for customers. This week, we expand upon that video with a useful tip for filtering your list of customers using an email address.Hope you enjoy!Video tutorial: Want to learn more about Connectors?Check out these resources:Connectors space on the Community Help Center: Understanding Connectors

Hey Front community!We’re thrilled to showcase a new example of leveraging Front Connectors to process refunds in Stripe directly from your Front inbox. The best part is, the full walkthrough takes less than 15 minutes and there is no coding required! This setup involves just 3 app requests and 1 macro, allowing teammates to easily select the customer, the payment to apply the refund to, and the amount to refund. Teammates will also see a confirmation message once the refund has been successfully processed in Stripe.  Pre-requisites:Before diving in, make sure you’ve done the following in Stripe:Have access to your Stripe dashboard We recommend switching to your

Hi, I am setting up a new support portal, and started an Enterprise Trial so that we would have access to application requests so that we can hit our custom API. After setting up an app request, testing it successfully (“Test Successful”), and the status is “Ready,” it is NOT surfacing when selecting the “Select app request” action in a new macro/rule workflow. See the screenshots below.This is the app request, showing “Ready” status: And when creating a new macro, it keeps telling me to setup a new application request, because it cannot find the ones I have created:Is there something wrong with my account setup? Why can’t I use the app requests in rules/macros?

Read original post:  

Read the original post here: