Skip to content

Feature: Save custom workflows in database #1497

@machadovilaca

Description

@machadovilaca

🚀 Feature Description

Is your feature request related to a problem?

I have a custom workflow I want to use in a platform based on this project. Every time I want to run that workflow, I need to input its details (repo, branch, path).

Describe the solution you'd like

Save custom workflows so they are easy to use later.

💡 Proposed Solution

Detailed Description: How should this feature work?

Save custom workflow details to the database.

User Experience: How will users interact with this feature?

After loading a custom workflow for the first time, it should show on Session -> Search workflows, under a Custom Workflows separator

API Changes: [If applicable] What API changes are needed?

The same listing API should work, but include custom workflows
Add new API to create and save custom workflows

🎯 Use Cases

Primary Use Case: Who will use this and why?

User Stories:

  • As a platform user, I want custom workflows to be persisted so that they are easier to use in the future

🔧 Technical Considerations

Component: [RAT System / Ambient Agentic Runner / vTeam Tools / Infrastructure]

Implementation Approach: [High-level technical approach]

Dependencies: [Any new dependencies or integrations needed]

Breaking Changes: [Will this introduce breaking changes?]

📊 Success Metrics

How will we measure the success of this feature?

  • Metric 1: Custom workflows are persisted
  • User feedback: I can easily reuse previously loaded custom workflows

🔄 Alternatives Considered

Alternative 1: [Description and why it was rejected]

Alternative 2: [Description and why it was rejected]

Do nothing: [Consequences of not implementing this feature]

📋 Additional Context

Screenshots/Mockups: [Add any visual aids]

Related Issues: [Link to related issues or discussions]

External References: [Links to similar features in other projects]

✅ Acceptance Criteria

  • Feature requirements clearly defined
  • Technical design reviewed and approved
  • Implementation completed and tested
  • Documentation updated
  • User acceptance testing passed
  • Feature flag implemented (if applicable)

🏷️ Labels

  • Priority: [low/medium/high]
  • Effort: [S/M/L/XL]
  • Component: [frontend/backend/operator/tools/docs]
  • Type: [new-feature/enhancement/improvement]

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions