When a workflow has an API Call step, Kolleno keeps each request that the step sends. Use this record to find out why an external system did not receive data from a workflow. To set up the step, see Make an API Call with Kolleno Workflows.
Where to find the API calls
Open the timeline of an enrolment from one of these places:
Workflow editor: click Executions, then select a record.
Customer Hub: open the previous workflow enrolments, then select an enrolment.
A note on the customer timeline: click
..., then View workflow enrolments, then select a row. This list also shows active enrolments.
If the enrolment sent API calls, the timeline has an API calls (n) tab. A red error icon on the tab means that the latest call failed.
Read an API call
The newest call shows first. Each call shows the status code, the method and URL, the time, the duration, the step name and the error, if there is one. No response means that no response came back, for example because of a timeout.
Click Show request and response to see the two bodies. Use the copy icon to copy a body exactly as it was sent.
Kolleno records only the API Call step. Connector steps, for example a note push to NetSuite, do not show here.
What Kolleno keeps
The details of each call, while the record is in the workflow and for 60 days after it leaves the workflow.
The latest 50 calls, while the record is in the workflow.
No request headers. Secret values in the URL show as REDACTED.
Common failures
What you see | What to do |
No response | Make sure that the URL is correct and that the external system is available. |
401 or 403 | Check the authentication of the API Call step. |
400 or 422 | Compare the request body with the documentation of the external API. |
500 to 599 | Kolleno tries again on a later run. If the error continues, contact the owner of the external system. |
The body is not valid JSON | Correct the body of the step. See Using Template Variables in API Request Bodies for Workflows. |