Overview
Execute Mandala workflows programmatically from your own applications.
Both official SDKs wrap the same underlying API: authenticate with a workspace API key, then trigger and monitor workflow executions from your own code, with async support, automatic rate-limit backoff, and usage tracking built in.
Both SDKs still ship under their pre-rebrand package/class names (mandalastudio-sdk/MandalaClient and mandalastudio-ts-sdk/MandalaClient) -- see the real install commands and names on each SDK's own page below.
Python
pip install mandalastudio-sdk -- for Python 3.8+ applications, scripts, and services.
TypeScript / JavaScript
npm install mandalastudio-ts-sdk -- fully typed, works in both Node.js and browser environments.
When to Use an SDK vs. the API Trigger Block
Reach for an SDK when a workflow needs to be called from your own codebase -- a backend service, a script, a CI job -- rather than from another Mandala workflow or an external webhook. If the caller is another system entirely outside your own code (a third-party webhook, a no-code tool), the workflow's own API trigger is usually the simpler integration point instead.