🌱 Help Us Grow

When collections are listed at the top, clicking on them displays all collections correctly. However, if a collection folder name starts with a letter like ‘T’, we need to scroll down to locate it. Additionally, if that folder contains multiple flows, they do not appear properly. To avoid confusion, there should either be a ‘Go to Top’ option or a scroll bar for collections, as well as a scroll bar for the flows.

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.

There are actions which includes callback url as input parameter and responds to the url(webhook url) when a task is completed For ex, in scraping when the scrapping is completed the api sends respond to webhook url

When users click on “Request an App” in the Integration page, a form opens to collect details for new app integrations. Currently, it allows submission even if the “Plugin Name” and “Use Case” fields are empty, leading to incomplete requests and confusion. These fields should be made mandatory, and if a user tries to submit the form without filling them, a clear validation popup should appear indicating that both “Plugin Name” and “Use Case” are required before submission. Also, the field label “Plugin Name” should be changed to “App Name.” When users click on “Request an App” and then see a field labeled “Plugin Name,” it can cause confusion since they are expecting to request an app, not a plugin. Renaming it to “App Name” will make the form wording consistent with the action the user is taking, making it clearer and more user-friendly.

if we were able to write code in the visibility condition then we can implement better ui/ux.

While adding an action -> I chose google sheet -> selection action 1 -> but then I realised that I should have selected option 2 -> but there is no option to go back. There must be an option to go back until and unless I save the action.