🌱 Help Us Grow

We can increase the time limit for a specific action so that the next steps do not run until the required action is completed. Until then, the remaining steps will stay on hold — similar to a human intervention step but automated.

Currently, trashed workflows still appear in the main workflow list, making the workspace cluttered and harder to navigate. By introducing a separate “Bin” folder, all deleted or trashed workflows can be automatically moved into this folder, keeping the primary workflow collection clean and organized. This improvement will benefit all users, especially those managing multiple workflows daily, by reducing visual noise and improving workflow management efficiency.

If any field is required while creating a connection, the placeholder example should not include an asterisk (*). The required indicator should be shown only in the field label, not inside the placeholder text, as this can create confusion for users.

Whenever I duplicate an action, the duplicated action should be named Copy 1, Copy 2, etc., instead of (1).

When setting up an OAuth 2.0 connection, users need to fill in multiple fields. However, when they click on one field, the previously opened field closes, which can be confusing. To avoid this confusion, we should clearly mention what needs to be entered in each field by adding a short hint in brackets next to the field heading (for example: Client ID, Client Secret, Redirect URL, etc.). This way, users can easily understand what information is required without getting confused while switching between fields.

I want an option in the visibility section that says “SaaS Verified and Listed”, where I can tick a checkbox once my app gets listed. When I check this box, it should automatically update in the database (reflecting the app’s verified status), and on the integration page, a verified symbol (like a checkmark or badge) should appear next to the app name.

My suggestion for viaSocket enhancement is to introduce a version control system in flows, similar to GitHub or Google Docs. Use case: If a user updates an existing flow and later realizes that the previous one was better, there should be an easy option to revert/restore to the previous version. Each flow should maintain a version history with details like timestamp and who made the changes. This would make both debugging and rollback much easier. Example: Suppose I created a flow that handles customer form submissions. If I accidentally delete some actions in it, I should just be able to click “Revert to Version - [Date/Time]” and restore the earlier stable flow. I believe this enhancement will make viaSocket more powerful and user-friendly.

Need support for the longer video on Instagram, Facebook, Twitter, LinkedIn, and YouTube. The video will be sent to the queue process and processed it and then the flow will be in paused once the process completes; the flow continues.

In DH, whenever I search for an app it doesn’t show the results until it refreshes the whole page.

This would really help clients ya fir users who use multiple tools and hate manually updating information in each one. With 2-way sync, changes in one app would automatically reflect in the others, saving time, avoiding mistakes, and making workflows way smoother. It would be especially useful for anyone choosing between viaSocket or any other automation tools (Zapier, n8n, Make, etc).

When we click Take Help with AI, the flow should remain open. The AI tab should open on the left side of the screen. Currently, the flow minimizes instead, which breaks the continuity of work because you lose the view of the flow.

When we create plugins for apps that generate images or videos, the processing time often depends on the prompt and can take longer. However, viaSocket has a 30-second response limit, which causes an error due to this time gap and delayed response.

When working inside a workflow (e.g., Folder A → Workflow 1) there’s no quick way to go back to the folder’s workflow list — the only option is to return to the home page. This forces extra clicks, breaks flow, and slows down switching between workflows in the same folder.

viasocket help should be passed from the backend as it is required in every sample data of each trigger

This trigger allows users to create and customize a form directly within the viaSocket. When the form is submitted, it instantly activates the flow and passes the submitted data for further processing—enabling easy collection and automation of actions without manual work.