Have something to say?

Tell us how we could make indie.money more useful to you.

Completed

Webhook URL Not Clearly Visible or Identifiable

Issue The webhook URL in the Run/Connections section is not clearly visible or identifiable. The link appears small and visually similar to normal text, making it difficult for users to immediately recognize that it is a webhook endpoint. As a result, users may overlook it or realize only later that it is a webhook URL. Expected Result The webhook URL should be more visually prominent and clearly identifiable. Possible improvements include: Increasing the font size or visibility of the webhook URL. Adding a label such as β€œWebhook URL”. Using a distinct UI element (button, highlighted field, or copy button) to clearly indicate it is an endpoint link. This will help users quickly recognize and use the webhook without confusion.

0x92a145E1f0c9d561d19AaBFA4df5826cA3cc4fAB about 1 month ago

Completed

Subflow Dependency and Token Handling Issues in Marketplace Workflows

Issue: Both main workflows and subflows are visible separately in the marketplace. When a main workflow depends on a subflow, users must discover and purchase both the main workflow and the required subworkflow. This creates a major usability issue. In a marketplace with hundreds or thousands of workflows, users cannot easily identify which subworkflow is required for a specific main workflow, making discovery and correct purchase impractical. Additionally, workflows that use subflows require separate token loading for both the main workflow and the subworkflow. This adds unnecessary friction and confusion for users, since they must manage tokens across multiple dependent workflows instead of handling the execution as a single unit. Expected Result: Subflows should be treated as internal dependencies of the main workflow, not separate items users must manually find and purchase. The platform should: Bundle subflows automatically with the main workflow, so users only purchase the main workflow. Hide subflows from the marketplace or mark them as internal dependencies. Automatically install required subflows when the main workflow is purchased. For token handling, the platform should implement a single token loading mechanism. When a user runs or purchases a main workflow, the system should automatically calculate the total token cost including all dependent subflows and allow the user to load tokens once for the entire execution. This ensures a smoother and more intuitive user experience.

0x92a145E1f0c9d561d19AaBFA4df5826cA3cc4fAB about 1 month ago

Separate Credentials Management Page for Producers

Issue : Currently, producers do not have a centralized place to manage their credentials. Credentials are tied within workflows, making it difficult to view, update, or manage them efficiently across multiple workflows. Request: Introduce a dedicated Credentials Management page for Producers where they can: View all credentials in encrypted format. Sensitive values should not be visible. Add new credentials Edit existing credentials without revealing the current values. When editing, the system should only allow replacing old credentials with new ones, not displaying the stored secrets. Delete credentials This will allow producers to manage credentials centrally and reuse them across workflows efficiently.

0x92a145E1f0c9d561d19AaBFA4df5826cA3cc4fAB about 1 month ago