Launched this week
ModuleX
AI workspace that’s already connected to everything
285 followers
AI workspace that’s already connected to everything
285 followers
ModuleX is an AI workspace already connected to 200+ integrations. Describe what you want, and your assistant answers with your data, acts through your tools, and turns the work into a visual workflow your team can edit together. If you want, it pauses for your approval before a step touches a customer. No API-key hunting: for a set of premium tools we bring the keys, or bring your own at zero markup. No empty canvas, no setup tax.
The multi-account same-tool piece is the interesting one. Once an assistant can touch ten Gmail or HubSpot accounts, setup tax becomes an identity problem: which account, which credential, which deployed version, and what proof survives after the run.
Do approvals scope per account/workflow, or only per step?
ModuleX
@blah_mad
Right call flagging it — once an assistant can touch ten accounts of the same tool, the friction stops being "connect it" and becomes "which identity is acting, and can you prove it after." We split that into three layers on purpose:
Binding is deterministic, not improvised. Which account/credential a step uses is pinned at build time on the node, and which deployed version ran is an immutable snapshot — every run records the exact version it executed. So "which account, which credential, which version" is configuration you can read back, not a decision made in the moment.
Approval is the separate, runtime layer. Today it's scoped per action — write/destructive tool-calls surface for confirmation while reads pass through. Standing approval policies that scope per account or per workflow (e.g. "this assistant may act on the support inbox unattended, but never the founder's") are exactly where we're taking it next — that account/workflow granularity is the right shape and it's on the roadmap, not shipped yet.
Proof is run-level today. Each run keeps the version, trigger source, who initiated it, full input/output, and timestamps. The next layer we're surfacing is per-call credential attribution stitched into one authorization view — the credential-level plumbing already exists; we're exposing it.
Short answer to your direct question: binding scopes per account + per workflow + per version; approval scopes per step today, with per-account/per-workflow approval policy as the next step.
@sezerufukyavuz This is the right split. I’d surface that authorization view before the action runs: account, workflow version, policy, and proof to be written. If a customer asks “why did this assistant touch this inbox?”, can they answer from one run view today?
Mailwarm
How do you handle authentication and permissions across tools, like does each teammate connect their own accounts or is it one shared workspace connection?
ModuleX
@thamibenjelloun We support both.
Some connections are shared at the workspace level, and some stay tied to the person who connected them. Then you can control which workflows are allowed to use which connection.
We didn’t want every workflow to start with wait, whose account is this using?
That templated-payload preview is exactly what I'd want - seeing {{drafted_message}} resolved beats approving a blind 'send.' One edge case for a support queue: if a variable resolves to the wrong record or comes back empty at run time, does the approval card surface the raw resolved value so I can catch a bad merge before approving, or could I wave through a payload that looks fine in the template but renders broken downstream?
Macaly
no setup tax + managed keys is a real differentiator 🙌 the approval gate before touching a customer is clever
ModuleX
@petrkovacik Thanks🙌
Managed keys get you past the setup mess. Approvals kick in only when the workflow reaches a step that actually needs a human call.
My Drawer
ModuleX
@furkanksl yes,losing the thread between tabs is the worst. really glad it lands 🙌 thanks.
ModuleX
@furkanksl You'r right :)
Congratulations on the launch! 🎉
ModuleX looks really promising. I like how it brings everything together in one place, so you can work with your data, use your tools, and build workflows without jumping between different apps.
Excited to see how the product evolves! 🚀
ModuleX
@beyza_kaynar Thank you 🙌 means more hearing this from an old teammate. that app-switching thing is basically what we built ModuleX to fix, pulling the context that's already in your Slack, Gmail, and CRM and actually acting on it, without the team losing the thread. still early days. let's catch up soon 🚀