Skip to main content
Pulse workflows are chains of small, reusable steps. Each step returns an ID that lets the next step reuse work instead of re-uploading or re-processing the same document.

The Golden Path

ID Handoffs

Extract -> Schema

Extract -> Tables

Extract -> Split -> Schema

Async Chaining

When you set async: true, wait for completion before passing the result to the next step.

Common Mistakes

A job_id is for polling. After the job completes, read the completed result and pass its extraction_id into /schema, /split, or /tables.
Downstream steps need saved extraction artifacts. Keep storage enabled when you plan to chain.
If the target pages are always known, pass pages or a table page_range. Use Split when topic location changes by document.
Schema is great for named fields. Use Tables when preserving row and column relationships is the product.

Pipeline Overview

See supported API pipeline shapes.

Moving from Platform to Production

Generate chained SDK calls from the Playground.