Enhanced error handling for API Request actions

We're excited to announce a significant improvement to our API Request actions with flexible error handling.

Note

Video UI outdated: The video shows the error handling option as "Apply standard error handling?". This has been updated to "Stop on error" in the current UI.

Previously error handling behaviour

• Zap runs would always run successfully, regardless of the API’s response status.
• The API response included error information such as the status code.

New and improved error handling behaviour

You can now choose how errors are handled:

• Standard error handling:
  • Zap runs will error if the app’s API does not return a 200 (OK) status code.
  • Zapier automatically attempts to refresh expired or invalid authentication tokens.
• Alternative error handling (default):
  • Zap runs are always successful, regardless of the API’s response status code.
  • The API response will always include the full response data, containing information about the error code, message, and status.

To use this feature, navigate to your API Request actions and select the desired behavior using the "Stop on error" field. The default settings is set to “No”. 

Benefits

• Increased flexibility: Tailor error handling to your specific API and workflow needs.
• Improved control: Gain finer-grained control over how Zaps respond to API errors.
• Enhanced debugging: Access detailed error information for easier troubleshooting.

This new feature provides greater control and flexibility when integrating with APIs, making your Zaps more robust and reliable. Learn more creating API Requests actions.

Note

This information was accurate at the time of publication. Please check out the latest product update notes for any updates or changes.