orchestration-solution-builder

Create a provider, then a router agent and a support agent via the orchestration agents API, bind capabilities like lookup_order and escalate_to_human, and compose a workflow from the customer-support template. Test agents individually before wiring them into the workflow.

Create providers first, then agents, then capabilities, then the knowledge base, and finally workflows. Dependencies enforce this sequence — creating out of order causes validation failures or silent misconfigurations.

Uploading documents creates chunks but does not generate embeddings. You must explicitly call POST /knowledge/embed after uploading, and ensure an embedding-capable provider like Voyage or OpenAI is active — Anthropic does not offer embeddings.

No. isSystem is reserved for Resparkable core machinery and makes rows undeletable, undeactivatable, and excluded from backup/export. App agents must seed with isSystem: false using an idempotent upsert keyed on slug.

A single agent with capabilities works for chat-based interactions. Use workflows only when you need multi-step processing, routing, approval gates, or parallel execution — simple solutions should not be over-engineered.

PATCH writes to draftDefinition only; schedules and triggers keep firing the previously published version. You must call POST /workflows/:id/publish to snapshot the draft as a new live version.