🌱 Help Us Grow

Why it’s useful & what it improves: Replace workspace notes with a visual canvas where users can loosely connect apps to draft what the automation will look like -like an ER diagram for workflows Notes don’t convey flow. A canvas helps automation experts explain ideas to clients, enables quick ideation, aligns expectations early, and reduces rework before production builds. This will also helps the experts to promise only that could be delivered and will improve the retention rate , because the user will connect and engages in a thing which is specifically built for them and in front of them.

Users think in problems, not workflows. This reduces discovery friction, speeds setup, and boosts activation by letting users install the right automation instantly - no website hunting.

It reduces confusion, simplifies actions, and improves usability by giving users one clear entry point and consistent navigation.

There should be a cURL importer option in the reusable component, and if the cURL contains pagination-related parameters, those parameters should be created automatically.

I created and published a template, but it is not showing in the ViaSocket template section when I search using the app name. However, the template is visible on the ViaSocket home page under the Templates section.

Number of integrated apps shown in the ViaSocket integration search differs from the count displayed inside ViaSocket.

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