Connections, auth and API

How do I use an HTTP call's response to decide where the workflow goes next?

Write the response into a hidden field with Update an item, then route on that field with a Goto or condition in a later step.

How-to

Short answer: Save the response in a hidden field on the item, then route on that field in a later workflow step.

Why it happens

  • The HTTP response lives inside the integration run. The workflow can't see it until you write it back into the item as a field value.
  • The integration fires from a workflow step, so the check on that field has to sit in a step after that one.

How to fix it

  1. Have the external API return a clear status, for example Success or Failed in the response body.
  2. Add a hidden field to the process form, for example API_Response_Status.
  3. In the integration, after the HTTP connector action, add the Kissflow Process action Update an item.
  4. Map the trigger item's ID and write the response value into API_Response_Status.
  5. In the workflow, after the step that fires the integration, add a Goto or a step condition that checks the field, for example API_Response_Status = "Success".
  6. Send the item forward when it succeeds, and back or to an exception step when it doesn't.

Tip

Keep the field hidden from users, or read-only, so nobody changes the value by hand.

Related answers