Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!


If you have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Add a new idea Subscribe
Status Already Exists
Workspace Nintex Automation Cloud (formerly Nintex Workflow Cloud)
Categories Xtensions
Created by Guest
Created on Mar 6, 2019

RELATED IDEAS

Support non-OK status-code in xtensions

Currently if a xtension responds with a code other than 2xx the call is considered to be a failure.

However many APIs legitimately return a status-code other than 2xx. For example if you query a service and no results are found, many APIs return 404 - "Not Found". This is a valid response and I would like to react on this response within the workflow. Many times this would result in either creating a new record (if a query returns 404) or updating an existing record (if a query returns 200).
  • ADMIN RESPONSE
    Sep 7, 2022
    We're reviewing this request internally.
  • Attach files
  • Admin
    Peter Byun
    Reply
    |     Mar 27, 2024

    The Error Handing feature is currently under development and will resolve this issue. Changing status to [Already Exists]

    3 replies
  • Guest
    Reply
    |     May 26, 2023

    I agree, I would like to be able to handle all response types on the custom xtension. Mainly 404's, 500's. In my case both of these values need to send emails out to customers to resubmit a form.