Hey everyone — I just updated the Error Automation via integrator.io APIs template to make it more flexible, easier to use, and better aligned with real-world error handling needs.
What’s new:
I've made several improvements based on internal use and customer feedback:
All custom filter fields are now optional — including flow id and step id
Expanded filtering support for error message and error code
Smarter logic for handling different combinations of filter values
Updated flow descriptions and in-app documentation for clarity
Simplified setup — you no longer need a separate export bubble for every flow id + step id combination — one export can now handle all your rules
How it works now:
After installation, go into each flow’s export step and use the custom settings to define which errors should be retried or resolved. You can enter:
Flow id — to scope to a specific integration
Flow step id — to target a specific export/import step
Error message — to match errors containing a keyword
Error code — to match specific system error codes
All fields are optional. The logic now supports any combination of filters, giving you more control over how errors are handled.
Examples:
No filters entered: All open errors from all flows are retried or resolved.
Only flow id provided: Errors from that flow are processed regardless of step or message.
Only error message provided: Errors across all flows that contain that message are processed.
Flow step id + error code: Only errors from that specific step that match the code are processed.
All fields provided: The rule applies only when all conditions match, giving you pinpoint targeting.
This replaces the old behavior where you needed one export bubble for every flow + step combo. Now you can define multiple rules in a single export and let the logic handle routing.
Flows included:
Auto retry – Fetches errors and retries records based on your filters
Auto resolve – Fetches errors and marks them resolved if they meet your criteria
Template name:
Error automation via integrator.io APIs
Available now in the Marketplace
Let me know if you have questions, feedback, or want to see additional functionality added.
I installed this template for the exact reason you discuss. I have integrations that fail when trying to connect to a website. In my error messages, I commonly see error codes 500, 521 and 522. They all seem to be related that the server didn’t respond and timed out. Sometimes I can retry them and other times I can only resolve them. It seems to depend on whether it is at the beginning of the flow or somewhere in the middle. If I resolve an error in the middle of the flow and I could have retried, am I going to lose that data? If so, then I would always want to retry before resolving. How would I accomplish that?
If you resolve an error, then yes you would lose that record to the resolved tab and that error would never try again. If you want to always retry, then you would only use the "Auto retry" flow and not the "Auto resolve" flow.
It filters at runtime, not design time since there is a lot of logic built into the preSavePage script and the output filter. All of this logic isn't executed with a preview call, and the preview call fetches all flows in the account. The reason being, in the settings, you could have provided no flow ID, in which case this would auto-retry or auto-resolve all errors in your entire account. As you add more criteria, the output filter handles which flow IDs and import/export IDs should remain going forward.
No option currently to put a wildcard, but the current message you put in does a contains operand, not an equal operand. So if you put “ERROR: Client: ALL13, Item: “, then it will look for messages that have that in it.
What’s new:
How it works now:
Examples:
Flows included:
Template name:
