🌱 Help Us Grow

I’m facing an issue with the “List All Employees” trigger in the Keka plugin. When I test the step, it correctly returns all 5 employees with full data.But when I run the flow live, the output changes:Only one employee record is returnedMost fields come back empty, or only the field labels/strings appear instead of actual values. This is breaking the loop logic and all downstream actions.

When working inside a workflow (e.g., Folder A → Workflow 1) there’s no quick way to go back to the folder’s workflow list — the only option is to return to the home page. This forces extra clicks, breaks flow, and slows down switching between workflows in the same folder.

We need an in-built plug that can generate short videos directly from a text prompt or from a sequence of images. This will allow users to create social media ads, short promo videos, and automated content inside viaSocket without relying on external tools.

Currently, trashed workflows still appear in the main workflow list, making the workspace cluttered and harder to navigate. By introducing a separate “Bin” folder, all deleted or trashed workflows can be automatically moved into this folder, keeping the primary workflow collection clean and organized. This improvement will benefit all users, especially those managing multiple workflows daily, by reducing visual noise and improving workflow management efficiency.

Problem: Custom API actions for specific apps require repeated HTTP setups and separate authentications even when the app is already connected. Improvement: Add a “Custom API Call” module inside each app that uses the existing connection automatically (no extra auth or headers needed). Example: A Google Sheets Custom API module could call any Sheets endpoint directly using the connected account, similar to HTTP but without manual token setup.

Problem: The text-to-image module is locked to the SeeDream model, limiting output quality options. Improvement: Add a model selection dropdown so users can choose between multiple image models (SeeDream, Gemini/NanoBanana, DALL·E, Leonardo/KREA, etc.). Example: For high-detail branding images, users could select NanoBanana, while simpler designs could still use SeeDream for faster or cheaper generations.

Problem: Current text-to-image module only accepts text prompts and can’t take any image as input. Improvement: Add an optional image upload / image URL input field alongside the prompt to support image-to-image or image + text generation. Example: Map logo URLs from Google Sheets into the module to auto-generate branded merch visuals by combining text prompts with uploaded logos.

When I working on js code i write a prompt the slider size increase and my chatbot page is below the page i am not able to see my chats

My idea is useful because it solves a real problem that many people face: reviewing failed workflow runs quickly and accurately. Anyone who manages automations—developers, analysts, or operations teams—would benefit from this, because they often need to check why something broke. The feature should work in a simple, intuitive way: whenever a user selects a filter like “failed steps,” the View History should instantly show all matching failed runs without confusion or missing data, making troubleshooting faster and stress-free.

Users should be able to view sample output data and available variables of an action before connecting the app. This helps users verify whether the required data is available before purchasing or authenticating an app. Currently, users must connect first, which often leads to wasted effort if the needed variables are not present.

1.If the reusable component name in the component section is in the wrong format, a message should be shown saying: ‘Component name should be in this format. 2.In the parameter section, we can suggest the list or types of values that can be passed in the parameter if the user enters a wrong value in the sample data.

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.