Launch a new Ironclad workflow from a specific template with pre-filled field values via the Ironclad API.
domain: developer.ironcladapp.com · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Obtain OAuth credentials scoped with the public.workflows.createWorkflows permission and identify the target template's ID (assigned when the workflow design is published).
Look up the template's field schema to find each field's system-generated Field API Name, which is required to target the correct field when prefilling data.
Build the launch request with the template ID and an attributes payload mapping Field API Names to prefill values, using multipart/form-data instead of raw JSON if attaching files at launch time.
Call the synchronous create-workflow endpoint to launch immediately, or the bulk/async launch endpoint when launching many workflows at once.
Capture the returned workflow ID and verify prefilled values landed on the expected fields by retrieving the workflow record afterward.
Known gotchas
Field API Names are auto-generated per field and can change if a field is deleted and recreated in the template designer — don't hardcode them without periodically re-validating against the current schema.
Prefilling a field that doesn't exist on the target template, or supplying the wrong data type, generally fails request validation rather than being silently ignored — validate payloads against the live schema first.
Large synchronous launches with many attributes or attachments can hit request-size or rate limits; use the bulk/async launch pattern instead of looping single synchronous calls for high volume.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?