Creating an integration

Updated 1 day ago by Abhiram

To see and create any integration in Kissflow, integration must be enabled in Flow Settings. If you don’t have sufficient permission to access this page, contact your Super Admin.

There are two ways you can create your Kissflow Integration from scratch. 

  1. In your Kissflow top navigation bar, click Explore. Under Explore all flows > Create new tab > click + Create new integration button.
  2. Alternatively, access your profile picture on the top right corner and click Integrations. Under the All integrations tab > click New integration button. Provide a name and description for the integration.

Setting up a trigger

To create a trigger step, follow the steps below:

  1. Select your connector. The integration workflow will be triggered based on the event that occurs in this connector.
  2. Select your trigger event. This will be the event that occurs in the selected connector that triggers the integration.
  3. Authenticate your connection. Authenticate the connector by setting up a connection. You can link to your Kissflow account or use another Kissflow account to authenticate the connector. Internal connections are established using the Access key and secret token based authentication. For third-party app connectors, authenticate the connector account using OAuth.
    To create connections, go to Integrations > Connections, and click New connection.
  4. Configure your trigger step. Customize your connector app to send data of your preference.
  5. Test your trigger. Test your trigger output to see if the trigger connector is properly configured.

If you encounter any errors while setting up the trigger, you will see all those error messages on the right side of the page. You can use this information to troubleshoot errors.

Even if the Access key associated with your trigger connection is deleted or turned off, your integration trigger will continue to operate.

Setting up actions

Similar to the trigger step, set up your action by choosing your action connector and event:

  1. Select your action connector. The action is activated by the trigger step or another action step.
  2. Select your action event. This will be the event that occurs in the selected connector when it is triggered.
  3. Authenticate your app connection. Authenticate the connector by setting up a connection. You can link to your Kissflow account or use another Kissflow account to authenticate the connector. Internal connections are established using the Access key and secret token based authentication. For third-party app connectors, authenticate the connector account using OAuth.
    To create connections, go to Integrations > Connections, and click New connection.
  4. Customize your action step. Customize the app data that you want to send over to your action connector.
  5. Test your action. Test your action output to see if it's working as expected.
    If the Access key associated with your connection is deleted or turned off, your integration action will be halted. To restart the action, update your connection with a new access key.

Naming your integration and connectors

When you create an integration, you must first add a title and a brief description to it. You can change these at a later stage by clicking the name of your connector and entering a new name. You can also update the description by clicking the () icon beside the title.

Similarly, you can change the name of each trigger or action steps. Just click the More options button () > Rename or click the default name of the connector, then enter your text in the field. Your changes will be saved automatically.

Turn on your integration

After you build your integration, the next step is to turn it on. You can click the toggle button in the upper right corner of the editor to switch it ON.

After your integration is turned on, it’ll automatically run your action steps each time your trigger event occurs. You can also view your integration’s Run history to see a log of all your successful and failed integration runs with data that goes in and out of each of your integration steps.


How did we do?