🌱 Help Us Grow

In DH, whenever I search for an app it doesn’t show the results until it refreshes the whole page.

The app description text after selecting an action or trigger at the flow side is too light and hard to read. Due to this low contrast, our app review was rejected. Updating the text color to a darker, more readable shade will improve accessibility, user experience, and help prevent such issues in the future.

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

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.

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.

Recently, I’ve been working on a complex flow, and now I need to update Slack channels in around 10 similar flows. So, I was wondering — can’t we build an enhancement for this? Basically, the idea is: I should be able to download a flow’s definition in JSON format, then search and replace specific values (for example, change “slack-testing” to “gtwy-test”), and finally upload the updated JSON back to the same org as the new flow definition. For example, if I have a flow with multiple steps, and I need to update all instances of the Slack channel “slack-testing” to “gtwy-test”, I could simply: Download the flow definition in JSON format,Search for “slack-testing” and replace it with “gtwy-test”, andUpload the modified JSON back to the org.

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.

the color of the log out button should be light red , it is not looking good in dark mode , kindly change it

we want the functionality to use npm or import package to implement some very usefull plugs or inbuilt tools ex: mongo db, text to speech, etc

one clicking yes no api calls for leaving workspace

Instead of deleting steps to change actions for the same integration provide simple button beside action name (could be a button or link button) called "Change" or "Change action" or "Switch action" or could be in the 3 dots menu that has (delete and duplicate options) or BOTH, then a list of actions for the same integration are listed to change/switch to another action, that is good for quick testing/prototyping and debugging.

IF condition is false and step didn't run, why we are showing sample data there?

Searching airtable in master org doesnt return all the plugs with that name, I wanted to find the public one, and cant find it by searching its name

Search - in MSG91 workspace. I search this flow Test - Unknown Error Alerts, this is the exact name of the flow but still ye search me bahut last me aa raha he, uske pahle 50 faaltu ke aa gaye

when i change the trigger . the change is not reflected immediately even after testing and updated the trigger.