🌱 Help Us Grow

The "Connection" and "App Details" buttons (located at the top right in the attached screenshot) are not functioning in Plugin Builder.

Add an option for handling errors and failures in nodes. There is no option to handle errors in nodes. An option to retry the action on failure can be added so that the workflow doesn't fail if any one part of it fails.

When a user loses internet connectivity, instead of showing a broken browser error or blank UI, viaSocket should display a branded offline screen with a short animation — for example, a plug getting disconnected from a socket (similar to Amazon’s offline dog screen). This screen should: Clearly tell the user that the issue is internet connectivity, not a viaSocket failure. Keep the user emotionally engaged instead of frustrated. Maintain brand presence even when the product is temporarily unreachable. This improves: User trust (they don’t think viaSocket is down). UX during failure states. Brand recall (even error screens look premium).

we should bring the one more built in tool -- phone validation as many clients required it and sometimes it is very hard to manage every edge cases from the js code. That's why, make this process simple to bring the phone validation built in tool.

There should be an option to create a template so that once a workflow is built, we can share it with someone else. They should be able to install it in their own organization, and then only need to do the configuration.

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