Run First Workflow
Choose or create a workflow identity, register external act paths, start a governed run, and verify compileHash in Runs.
Choose or create a workflow
A workflow in Blekline is a stable wf_ id plus policy and cell defaults. Your application keeps infer and decide; Blekline governs act when you start a run.
Pick one starting path:
- Create in the console when you are exploring Blekline or do not have an external orchestrator yet.
- Register from your application when execution already lives elsewhere. POST
/api/workspace/workflows(session) or use the console, then pass the sameworkflowIdon every act run.
Execution already outside Blekline
If you register from your application, keep execution on your stack. Register one Blekline workflow per governed act path, and call POST /api/workspace/cell-runs from that step with the same workflowId. Blekline does not host cloud workflow engines, durable worker fleets, schedulers, or agent runtimes.
Cloud-native control planes
- AWS Step FunctionsState machines and Lambda tasks; start a cell run from the act step.
- Azure Durable Functions, Logic AppsDurable orchestration and integrations; register the act branch you isolate.
- GCP WorkflowsConnector and HTTP steps; call Blekline when a step needs workspace policy.
Durable workflows and platform engineering
- TemporalDurable workflows you operate; one workflowId per governed act path in your workers.
- Argo WorkflowsKubernetes DAGs; trigger cell runs from the template step that performs side effects.
- Camunda, internal worker platformsEnterprise BPM and homegrown schedulers; HTTP at the act boundary only.
Developer SaaS and AI agent stacks
- LangGraphAgent graphs in your service; start a cell run when a node executes governed act.
- InngestEvent-driven and AI workflow functions; invoke cell runs from the act step.
- Trigger.dev, Hatchet, custom runtimesTask runners, queues, FastAPI, and agents. No Blekline plugin required.
Example registration body for an external act path:
{
"name": "payments-act",
"id": "wf_payments_act",
"description": "Act path for payments; orchestration and retries stay in your app or job runner."
}Set workspace environment variables
Export a token locally. Use your app origin when you develop against a local webapp.
BLEKLINE_WORKSPACE_TOKEN=blw_your_workspace_token BLEKLINE_API_URL=https://app.blekline.com
Install the client and inspect policy
Install the TypeScript SDK or call the REST API with curl. Confirm the workspace policy stage before you start a run.
npm install @blekline/client
import { BleklineClient } from "@blekline/client";
const client = new BleklineClient({
workspaceToken: process.env.BLEKLINE_WORKSPACE_TOKEN!,
});
// List workflows you created in the console (session cookie or bearer in the app UI).
const policy = await client.getExecutionPolicy();
console.log(policy.enforcementStage, policy.fleetMode);Start your first run
Open the workflow from step 1 and choose Run. The console calls POST /api/workspace/cell-runs with your signed-in session (or a workspace token with runs:write via x-blekline-workspace-token). Request body shape:
{
"workflowId": "wf_your_workflow_id",
"displayName": "First workflow run",
"executionTier": "act",
"toolCall": true
}Optional cellProfileId and clusterId apply after you Spin up cells.
Verify in Runs
Open Runs in the app. Select your run, confirm status, and copy compileHash for audit export. Execution metrics aggregate here once you have more traffic.