Documentation

What Malleable is, and how to go from a plain-English description to a running workflow.

The three layers (setup, execution, improvement), and why a workflow is a plan, not a script.

From a plain-English description to a published, running workflow in about fifteen minutes.

Your organization, who can see a workflow, run links, view-only canvas links, changing owners, and sharing app connections.

Common questions: coding, accounts, missing integrations, AI autonomy, failures, and data handling.

How Malleable handles your data, credentials, and third-party access.

Set up single sign-on with OIDC or SAML: Microsoft Entra ID, Google Workspace, or another identity provider.

What a workflow is and what it's made of: stages & components, hand-offs, sub-workflows, and data flow.

Building a workflow with Malleable, publishing changes (drafts and versioning), and suggestions.

How runs work: what Malleable can do during a run, how it behaves, and seeing what happened.

Test runs: try a workflow end to end before you publish, choose what happens in your other apps, and replay what happened.

Tables a workflow keeps between runs so it doesn't repeat work: adding memory, how runs use it, and fixing it.

Talk to Malleable in Slack, Microsoft Teams, the app and AI tools: ask about runs, get tasks done, and build or run workflows.

Every building block Malleable can put inside a workflow: triggers, actions, data sources, interactive pages, and flow control.

Workflows connect to thousands of tools: the most common ones, and how to connect them.

Connect Claude or any MCP client to Malleable: list, build, edit, and run workflows from outside the app.