🌱 Help Us Grow

When a user establishes the connection by clicking on the connection and searches for an app, but the app is not found, the "Request an App" button should be visible.

Enhanced Efficiency: Saves time by automatically suggesting workflows, templates, and steps based on user history, eliminating the need for repetitive task setup. Personalized Experience: Delivers intelligent, context-aware recommendations tailored to each user’s habits and preferences, optimizing their workflow process. Proactive Productivity: Anticipates user needs and prompts relevant actions or reminders, ensuring tasks are completed on time and preventing overlooked steps.

I was thinking we could start using reusable components. The good part is, once we set up a module, it can be used across the workspace. And whenever we update it, the changes will automatically reflect everywhere it’s used. This way, we’ll have a single source of truth and it’ll cut down a lot of maintenance effort

sometimes we save our projects as json files, and i want to move them here so if there is a json file that i can upload to open my project here it would be awesome, keep up the legend website!

Because of Dark mode, we can't see the text appearing on the screen. If dark mode, colour of text should auto change to white.

If user wants to delete thier MCP server, as of now we don't have that option. We can allow them to do so.

When a user on the viaSocket home page clicks on “Request App Integration”, the same pop-up from the viaSocket panel/dashboard should appear, with an additional option to schedule a meeting via a provided link.

Currently, whenever a flow fails, all workspace members receive the failure notification—even those not involved in that flow. Ideally, only members who have contributed or are part of the activity in that flow should receive the notification.

Notification about a bug related to API keys created from Account > Developer

Helga Moreno shared an updated article draft and requested feedback from Vaishali Raghuvanshi. The article is about automating processes in a co-working space using viaSocket.

Idea – Why not integrate an API testing mechanism (similar to Postman) directly into our ViaSocket DH section? This way, builders won’t need to switch tabs to test and return. Since we already have a DocStar engine, we could leverage it for this integration. → DH Suggestion.

Email discussing integration of Imagine.art with viaSocket marketplace

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.

Dark mode is not optimized for all pages yet. even if it gets optimized we need button to switch between normal mode and dark mode according to user preference.

This email contains a series of shared posts from LinkedIn