🌱 Help Us Grow

Your feedback fuels the future of viaSocket.💡

Share what you love, what’s missing, or what feels off - we’re listening. Every word shapes what comes next.✨

If you want to request a plug or modification in plugs, visit https://viasocket.com/integrations

Trending

  1. “A loop cannot be implemented within the trigger unless a cron-based scheduler is used"

    saves time and manual efforts Smart Escalation = Faster Response Smart Task Management

    Nandini S

    0

  2. while we fill the request for the plug the name and email feilds are required but other feilds are stated as not required

    Khushi R

    1

  3. go back option while adding action

    While adding an action -> I chose google sheet -> selection action 1 -> but then I realised that I should have selected option 2 -> but there is no option to go back. There must be an option to go back until and unless I save the action.

    Jay Panjwani

    0

  4. Improve App Request Form & Plugin Naming

    When a client requests any new app or integration, update the system so that the term “plugin” is replaced with “app name” throughout the form. Additionally, make all fields mandatory to ensure complete information. Add one more required field for Phone Number / WhatsApp Number so the team can quickly contact the client if clarification is needed.

    Diksha P

    0

  5. Make “Plugin Name” and “Use Case” required in the Request an App form, and rename “Plugin Name” to “App Name” for clarity.

    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.

    Prashant J

    0

  6. "Flow Date Bug: Update Issue Insight"

    On home page table -> click on any flow which is on top and come back, Now its updated date becomes NA and it goes at bottom

    Pushpendra A

    0

  7. "Efficient Issue Resolution Request"

    kindly look into this issue

    Rakshit S

    0

  8. "Fix Empty Payload: Trigger Dry Run First"

    when i click on retest flow , the payload seems empty. so first i need to dry run the trigger step.

    Rakshit S

    0

  9. App Search Requires Page Refresh

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

    Devesh S

    0

  10. option to write code in the visibility condition

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

    Harsh G

    0

  11. “Variable Popup Fix Needed”

    plug -> Test -> popup is not coming to change the variable values

    Pushpendra A

    0

  12. "Text Visibility Restorer"

    Chip is coming on the text I am writing, it's making almost impossible to see what I am writing.

    Ravi P

    0

  13. “Step Name Rename Issue”

    Not able to rename step name

    Ravi P

    0

  14. "Gateway Embed Connection Query"

    why is it asking me to connect gtwy , (I'm using gtwy embed)

    Rakshit S

    0

  15. "Chat Bot Error: Incorrect Action and Version ID"

    wrong action and version id passed in sendmessage(chat bot)

    Prayansh R

    0