Connectors

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.