Frequently asked questions¶
Do I need to know how to code?¶
No. You describe your process in plain English and the architect builds the workflow. When a step genuinely needs code, like a calculation or a strict data transformation, the architect writes and tests it for you.
Do the people running workflows need Malleable accounts?¶
The workflow owner does. Anyone who needs to run a workflow or take part in one can do so without an account, through a link, a Slack or Teams message, an email, and so on. See actors & hand-offs.
Can Malleable connect to my tool?¶
Almost certainly. We connect to thousands of apps via MCP, plus a number of integrations we've built, and we can also reach products through their APIs (web requests) or browser use.
Can I change a workflow after it's live?¶
Yes. Tell the architect what's different and it updates a draft you can review. You publish when you're ready, and runs already in progress finish on the version they started on. The system also proposes its own improvements as suggestions, drawn from background quality reviews and from real runs, that you review and approve, so the workflow gets better with use. More in editing & publishing.
What's fixed versus what does the agent decide, and how do I stay in control?¶
The shape of the workflow is fixed and repeatable: its stages, the steps in each one, and the tools it's allowed to use. Within that, the agent uses judgment on the parts that vary from run to run, like handling an edge case, drafting text, or choosing a branch you set up. It can only use what the architect built, so it can't go off and do something the workflow doesn't include. Where you want a person to make the call, the workflow pauses for you.
If AI runs every workflow, isn't that expensive?¶
Not the way you might expect. The plan is worked out ahead of time, so each run the agent just follows it instead of figuring everything out from scratch. This allows most Malleable workflows to run on very efficient models, resulting in speed and cost savings!
If an AI is involved, can't it take actions I don't authorize?¶
No. Your integrations and secrets never enter the agent's view, so it can only take the actions that were set up when the workflow was built, not new ones of its own. You can see everything it's able to do, laid out on the workflow canvas. Connections use the provider's own sign-in (OAuth), so Malleable holds a revocable token, never your password. More in security & data handling.
Can I control Malleable from another app?¶
Yes. Malleable exposes an MCP server, so Claude and other MCP clients can list, build, edit, and run your workflows from outside the app.