Review the information provided to diagnose integration errors.
You can view errors in the workflow run logs. See Checking the status of workflows.
Common or known errors
Response Message |
Reason |
External API call has returned an error: 400 Bad Request |
Review the API documentation and complete the following actions in the API block in Advanced Mode:
|
Length of the field [[name]] should be less than [[no of characters]]. | Ensure that the field that you map the response to has a sufficient character limit. |
No error occurs, but the response value will not be mapped. | If there is a hyphen in the response, use the following bracket notation: {{response["test-field"]} |
Error codes
Response Code | Reason |
400 Bad Request |
Bad request or issue with the message body. Refer to Common or known errors. |
401 Unauthorized |
Your credentials might be invalid or might have expired. Follow the steps for your integration in our vendor integration list to re-add your credentials in Configuration>Security>Credentials. |
403 Forbidden | You do not have sufficient privilege to access the vendor's API. Ensure that you have the correct access rights or administrator privileges to use the API. Consult the vendor API documentation in our vendor integration list. |
404 Not Found
|
The API URL used in the workflow is invalid. Check your API URL in the API block against the API documentation by going to Advanced Mode > Information > URL. |
405 Method Not Allowed |
This API call is not allowed, such as deleting something that can't be deleted, using an unsupported HTTP method (PATCH instead of PUT/POST), or interacting with the incorrect endpoint. Check your API URL and HTTP method in the API block against the API documentation by going to Advanced Mode > Information. |
409 Conflict |
These conflicts are most likely to occur in response to a POST/PUT/PATCH request and indicate that you are trying to do something that is not permitted, such as deleting or editing a read-only or reserved field, using a sting instead of an integer, or assigning a device to a user that does not exist. Check your request Body in the API block against the API documentation by going to Advanced Mode > Body. |
429 Too Many Requests |
Too many requests - too many requests have been sent in a given amount of time. Check your workflow schedule. |
500 Internal Server Error 502 Bad Gateway 502 Service Unavailable |
These error messages indicate a problem with the system. Please contact support and include the details of your error message. |
If you continue to receive errors, contact Support.
Comments
0 comments
Please sign in to leave a comment.