🌱 Help Us Grow

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 button or a process is initiated, a lot of time, there is no intimation or loading animation shown to the user, even though the process is running in the background. This causes multiple clicks of a button, which leads to multiple requests in some cases.

This action could potentially be very useful for the users. What it basically allows you to do is: Pick any field from any previous action's output, and then you can set it as a variable that can appear as an input field for all future actions. For ex: If a action outputs [{name: x, year: 2025}], we can just pick name and set it as a field. The name can be individually input in any action that appears later in the flow. This is especially helpful with complex JSON outputs as well as arrays.

When I’m taking help from AI and I open the flow action dropdown just to view the action names, the moment I switch back to the chat, the entire chat disappears. This is extremely frustrating because the context is lost.

In the text editor, formatting changes such as bullet points and other styles do not reflect while editing. If the formatting is supported, it should appear immediately; however, currently the changes are not reflecting in real time.

Currently, the help text appears below the input fields during user authentication. Instead, it would be more effective to display all relevant help text at the top of the authentication step. This would allow users to read and understand the instructions first, and then proceed to enter the required details such as API keys or secret tokens with better clarity and fewer errors.

When a user selects a Manual Trigger, the Connection Type should automatically default to No Auth during trigger creation.

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.