We received a question the other day from a potential client asking, “Can Forms On Fire connect to my system Jira?” and “If so, do you have any documentation for such integrations?” You may not be using Jira specifically but if you replace Jira with [Your System], the process of determining whether we can connect will be the same. Feel free to continue reading.
First, we confirm that we can integrate with Jira, either directly or through our connector with Zapier. And visiting Zapier.com is likely a good place to begin because Zapier connects over 1,000 systems, including Forms On Fire. Just visit the link above and search for your app.
Most modern cloud systems today utilize RESTful Web Services. This is a communication protocol (API) that I am not going to get into defining here. Know that Forms On Fire utilizes a full REST API. The documentation for the Forms On Fire REST API is located here.
Because there are thousands of systems that use REST APIs, we do not usually have documentation on any specific integrations, except by chance we document individual work done on behalf of a specific client, or in the chance we have written a blog post.
INTEGRATING FORMS ON FIRE WITH JIRA USING ZAPIER
Zapier alone has over 1,000 integrations, including Jira. It appears that Jira has enabled six triggers, four actions and 2 searches including:
New Issue (Via JQL)
New Issue Type
Add Watcher to Issue
Attach File to Issue
You can see all of these listed on this page and search for Jira:
You can also see the triggers and actions available for Forms On Fire if you search on the same page. We offer 1 trigger and 4 actions including:
New Form Entry
Update Data Source
Possible Examples using Zapier
In any two systems, you pair up the Trigger from one system into an Action in the other system. For example you could do something like:
New Project TRIGGER in Jira performs the ACTION to Create Task in Forms On Fire
New Issue TRIGGER in Jira performs the ACTION to Update Data Source in Forms On Fire
New Form Entry TRIGGER in Forms On Fire performs the ACTION to Create Issue in Jira
New Form Entry TRIGGER in Forms On Fire performs the ACTION to Attach File to Issue
There are many, many other things I could think of using to integrate these apps, these are just a few examples.
INTEGRATING FORMS ON FIRE DIRECTLY WITH JIRA
Both Jira and Forms On Fire have an OPEN API, making it possible to connect the systems directly together. This takes a little more time and understanding of how RESTful Web Services works. Most programming individuals and some non-programmers know how these work and can figure out how to connect the two systems.
Nearly every object of the Forms On Fire data model is available through our OPEN REST API. The documentation for this API is located here:
It appears that many objects for Jira are also available, and their documentation is located here:
If you want to find out if your cloud system has an OPEN REST API, simply type in Google a search such as:
REST API site:<YourCloudSystemURL.com>
Replace YourCloudSystemURL.com with the domain of your provider, such as Salesforce.com. If a lot of documentation comes up in the search results, it is likely your cloud system utilizes a REST API.
Notice how closely these match, such as GET and PUT and POST or CREATE? That’s because they both speak the same language: REST! 🙂
That being said, it’s possible, depending upon the authentication model for Jira, that we’ll need a server to intermediate getting a connection to Jira. If this is the case, a simple, free Google account can accommodate as such an intermediary server. I see many objects available in the Jira documentation…so rather than providing some examples…
…here’s the real questions. What do you envision integrating? What data do you want from one system to end up in the other? If you are interested, send us those requirements and we can create an estimate from our professional services team to integrate our system to yours for you. If you have people there who can do this, awesome!
Let us know how else we can help. Happy integrating!