Workflow components
Components are the building blocks inside a workflow's stages. The architect picks and configures them for you based on what your process needs. This is the full catalog it chooses from.
Triggers
Starts a workflow from a form or interactive page. The person kicking off the run fills in what's needed, and can hand the run off to someone else mid-stream.
Starts a workflow when another system sends an HTTP request to a dedicated URL. Use it to connect tools that can call webhooks.
Starts a workflow when an email arrives at a dedicated address. The email's content becomes the run's starting context.
Starts a workflow from Slack: a message in chosen channels, a direct message, or an emoji reaction, optionally filtered by criteria you describe in plain English.
Starts a workflow from Microsoft Teams: a message in chosen channels or a direct message, optionally filtered by criteria you describe in plain English.
Starts a workflow on a recurring schedule (e.g. every weekday at 9am), in the timezone you choose.
Actions
Performs one action in a tool Malleable integrates with natively: read a spreadsheet range, send a Slack message, create an Asana task, and so on. See the integrations reference for everything available. For a service Malleable doesn't integrate natively, use an integration action (MCP).
Sends an email from a template the architect sets up. It goes out exactly as written, with only the templated parts filled in from the run's collected data.
Calls an HTTP API, which is useful for systems Malleable doesn't have a built-in integration for. Supports JSON and file-upload payloads.
Runs a piece of code the architect wrote for your workflow: calculations, data transformations, or logic that's better done exactly than approximately.
Hands a focused task to a separate AI agent with its own instructions and tools, and returns the result to the run.
The same idea as a native integration action, for any service that exposes an MCP (Model Context Protocol) server. You choose which of the server's tools the workflow may use, whether that's one, several, or its whole tool set, and the agent uses them during runs.