Using the current Workflows builder is a constant source of frustration. The lack of execution history and detailed logging means there’s no way to understand what’s happening behind the scenes -when a workflow fails to trigger or doesn’t behave as expected, users are left in the dark for the most part.
For context, HubSpot offers this kind of workflows visibility natively and offers API access, while Intercom still feels limited and paywalled by comparison.
Troubleshooting becomes a guessing game, and it’s nearly impossible to track down issues or optimise workflows. The absence of API endpoints for reading, creating, editing, or triggering workflows make the experience feel clunky and restrictive.
Every attempt to build or debug a workflow is so painful and frustrating.
Could you please consider these features?
- Add a comprehensive execution history and detailed logging (including failed triggers and error details).
- Provide API endpoints to at least read workflows to help make it more manageable in the meantime. Though creating, editing, and triggering workflows would be awesome too.
These improvements are essential for making workflow management and troubleshooting bearable, and would transform the Workflows builder from a source of daily frustration into a powerful, reliable tool.