HTTP task should have an option to *not* throw an error on a 404

[mikebski]

The feature, motivation and pitch

When writing idempotent workflows, we often will do a GET on a resource to see if it exists and branch based on the result - if we get a 404 we create and continue with the new object and if we get a 200 we just proceed with the existing object.

This is a very common automation pattern, and we should support it there.

Alternatives

No response

Additional context

No response

[jeffbulltech]

Hey @mikebski thanks for bringing this up! I've added your feature request to the roadmap and sent to our engineering team for evaluation.