Skip to main content
Qlik Data Gateway upgrade REQUIRED by September 15 READ MORE

Getting Started with the Inphinity connector in Qlik Application Automation

No ratings
Showing results for 
Search instead for 
Did you mean: 

Getting Started with the Inphinity connector in Qlik Application Automation

This article is meant to help users get started on using the Inphinity connector in Qlik Application Automation.

Using the Inphinity connector in Automations allows users to read records stored in Inphinity, which can be the whole dataset as well as individual or multiple filtered records, as well as performing writeback to Inphinity.

To get started you will need to have an Inphinity forms instance.

Connecting to Inphinity Connector:

To connect the Inphinity connector you will to find the hostname of your Inphinity instance. For Inphinity SaaS this will be Notice there's no slashes or protocol assigned, just hostname.

Next you will need your Forms Instance ID as well as your API token. You can find these when you are logged into Inphinity and configure your form



  • Read Form Data: This block has an optional body parameter. This has to be a JSON list containing strings. The string has to be matching a record key. If it is provided, only records matching the keys will be returned. If not provided, every record in the dataset will be returned.
  • Save Data to Form: This block takes a JSON list of JSON objects. Each JSON object contains a parameter named "_key", which needs to be the full key of the row identifier of your form. Every other key in the object will be considered as a value of that row.


Usecases with the Inphinity Connector in Application Automation

This connector helps users of Inphinity Forms to achieve the following usecases:

  • Obtain changes made in the Inphinity Form and push these to third party systems. This can be done by creating an automation which pulls all records from an Inphinity Form using the Read Form Block and subsequently using a third party connector to update information in the third party system. This way changes made in Qlik Sense will be propagated to the correct systems.
  • Tracking changes in third party systems that need to be received a dashboard on Qlik Cloud. For example when a user modifies a field in Hubspot or Salesforce and this data needs to be visible in the Qlik Sense app. This works really well in combination with Incremental blocks that only provide only recent changes made in the third party system. After obtaining the changes, we can make use of the Save Data to Form block to send a JSON body with the Inphinity unique key provided as well as the fields that were changed.
Labels (1)

If you are as excited about this connector as I am, then you will be anxious to really dive in. So, I've created a very detailed document to help you envision a use and walk you through building it step by step.

Version history
Last update:
‎2022-07-14 03:40 AM
Updated by: