Build your first workflow¶
The fastest way to understand Malleable is to build something real. Pick a process you actually run, like an approval, a follow-up, or a weekly report, and give yourself fifteen minutes.
1. Describe your process¶
Create a new workflow and describe the process in plain English, the way you'd explain it to a new teammate:
When a sales engineer finishes a customer call, they paste in the call link. Read the transcript, find the documentation pages that answer what came up, and draft a follow-up email with the right links for them to review.
Don't worry about being complete. The architect starts building from whatever you give it and asks about the gaps, so you'll answer questions while stages are already appearing on the canvas.
2. Watch the structure take shape¶
As you talk, the architect lays out the workflow as a diagram: stages for each phase of the process, with the components inside them (forms, integration actions, emails). For the description above, you'd end up with something like:
This diagram is the thing you'll keep coming back to. Click any stage or component to see what it does, ask the architect questions to understand it, and tell the architect what to change. Nothing is precious: "split that into two steps", "the manager should approve first", "make the email shorter" are all normal requests.
3. Connect your tools¶
Ask the architect to connect the tools your workflow uses and it handles the secure sign-in for you. See integrations for what's supported.
4. Run it¶
Publish the workflow and run it. You can also test it as a draft before publishing. Depending on the entry points the architect set up, a run starts from a form, a Slack or Teams message, an email, a webhook, or a schedule. During the run, the agent works through the stages, asks for input when it genuinely needs it, and hands off to other people with an authenticated link when responsibility transfers, with no account setup needed on their end.
5. Change it¶
After a few real runs you'll notice things you want different. Tell the architect, and the workflow regenerates around your intent. You'll also start receiving suggestions, improvements proposed by background quality reviews and by the runs themselves, waiting for your review.
Start from an example¶
The best way to start is to chat and brainstorm with the architect. Browsing finished workflows is another good way in. The showcase is a gallery of complete example workflows (customer onboarding, manufacturing operations, retail, and more), each with its full diagram: the stages, who's responsible for each, the tools involved, and how runs move between people.
A few ways to use it:
- Find your sector and skim which processes translate into workflows. Most teams' "unique" process is more recognizable than they expect.
- Open a workflow's diagram and read it stage by stage; it's the same diagram you'll work with when building your own.
- Borrow the shape, not the details. If a showcase workflow is close to yours, describe yours to the architect and mention what should differ. You don't start from a template; you start from your intent.
Stuck?¶
If a step doesn't make sense or the architect misunderstood you, just say so in the chat. Disagreeing with it is a normal part of the loop.