When a workflow fails for any reason, is there a way to send a notification so that the user knows something failed without needing access to Gumloop? E.g., Workflow A fails because of reason XYZ, a Slack message is sent to my #error_log channel “Workflow A failed. Reason: XYZ. Link: w…”
I know it could techinically be done by wrapping every node inside an Error Shield, but that feels like a lot of work. And I know one could also turn a flow into a subflow node and put that into the error shield, but that seems like it can complicate things in other ways.
Hey @pedrocabassa! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
-
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}
-
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
-
Provide details about the issue—more context helps us troubleshoot faster.
You can find your run history here: https://www.gumloop.com/history
Hey @pedrocabassa – Yes, this is possible. You can use the Alert feature for this:
