🌱 Help Us Grow

Allow users to choose their preferred authentication method (e.g., OAuth login page, client credentials, API key, etc.) when connecting services, instead of enforcing a single flow. This way: Technical users (devs, admins) can pick client credentials / API keys for automation. Non-technical users can pick the login page flow for convenience.

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.

Frappe is a modern web framework with batteries included. (Frontend UI, Database ORM, Authentication, CLI, Low-code tools, etc). ERPNext is the flagship product built on top of Frappe for enterprises.

The current “Reset” button name is misleading. Users assume it will reset or discard changes, while in reality it only re-centers and adjusts the view of the flow canvas. This causes: Hesitation to use the featureMisinterpretation of its function Proposed Solution:- Rename the “Reset” button to “Fit to Screen”, aligning with common design and diagramming tools (e.g., Figma) Optionally add a tooltip: Centers the entire flow and adjusts zoom to make it fully visible.

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.

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.