🌱 Help Us Grow

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.

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.

WebFlow is announcing a free online conference

The email shares a screenshot of a UI design concept

The email discusses the changes in job design due to AI and the role of HR in reimagining job design

Email discussing integration of Imagine.art with viaSocket marketplace

Brighter button text improves visibility, accessibility, and user trust—especially in dark mode where contrast is key.

If any user haven't connected Response Block in the flow, don't show Response block in the Logs, that's making confusion from user POV.

The email discusses the growing shift towards AI in various industries

Email delivery failed due to recipient server not accepting connection requests

We should have a loop feature in the cron trigger so that specific nodes can be executed multiple times within a single cron run. For example, if a cron is scheduled, I want the ability to run certain nodes a defined number of times instead of just once. This will make cron-based workflows more flexible.

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.

Email about an idea being published on a roadmap