Connectors

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:  

This will help you make sure a Front conversation being linked to a JIRA issue will not go unnoticed. The idea here is to leverage our JIRA connectors through an app request rule that will automatically post comments in JIRA issues when those are linked to a Front conversation. Here’s how your rule should look like: This rule will trigger on app objects being added to a conversation, will check that the added app object is a JIRA issue, and will post a comment in that JIRA issue  This is the dynamic variable used to determine if the added

Hello.  I am looking for any suggestions on how to use system variables in Connectors.  I have a moderate amount of comfort working with APIs.  I have a Connector set up and working - POST requests are working and creating records in our third party app without issue.I cannot seem to be able to figure out how to pass system variables through our POST request.  I can create dynamic variables in the Connectors, but these do not seem able to access basic system data.  I have tried every variation I can think of - {{user.name}}, user.name, etc. but all this does is pass {{user.name}}, user.name, etc.to the created record.  I’m hopeful system variables can be passed through the Connectors and I am just missing something very obvious.  Any input is welcomed and appreciated.  Thank you!

As we’re in setup, does anyone have any good advice in terms of keeping it simple but impactful in terms of the connectors we’re building. How should we think about connectors and their applications within Front. We have a development team and want to make sure we’re prioritizing the right work for connectors. Looking for a framework to help us think about this prioritization.