Proposal: Enhancing Workflow and Action Visibility via API Integration to PlayBooks (External Project)

[sidPhoenix17]

Hi StackStorm Community,

I’m working on an open-source runbook automation project called Playbooks. While we currently operate using our own execution engine, we are exploring an integration with StackStorm APIs to address a specific use case and would love to get your feedback.

Use Case

I have seen some messages in the community where people are building their own UI to get the following:

• See list of workflows.
• Execute specific actions without running the entire workflow.
• Visualize individual actions within a workflow.

My understanding is that a richer UI helps with ease of use & improving adoption of the internal Stackstorm implementation within the company.

Proposed Solution

Integrating StackStorm APIs into Playbooks could provide the following capabilities:
-- List of workflows: See list of workflows in UI and search over them.
-- Workflow visualization: A detailed breakdown of all actions within a workflow.
-- Granular execution: The ability to run individual actions instead of executing the entire workflow.
This would complement StackStorm’s current capabilities by providing a more user-friendly way to manage workflows, making it easier to debug or execute specific steps from UI and improve adoption amongst your company's developers.

Questions for the Community

Does this use case resonate with others in the community?
Would such API enhancements align with StackStorm’s roadmap, or could this be an external contribution?

Invitation to Collaborate

We’re still in the early stages of exploring this idea, and I’d love to hear your thoughts or suggestions. If this aligns with your needs or interests, feel free to share insights or join the conversation.

To give a sense of the platform and UI, here’s a screenshot & a video of the current Playbooks UI:

Looking forward to hearing from you all!