Workflow
ConceptsA workflow automates document processing with triggers and steps. When a trigger fires (e.g., upload, webhook, schedule), the workflow runs configured steps such as parse, extract, or notify. Workflows enable event-driven automation without custom code.
Workflow Structure
| Component | Description |
|---|---|
| Trigger | What starts the workflow: upload, webhook, schedule, or manual |
| Steps | Actions to run: parse document, run extraction, send notification, call external API |
| Integrations | Connect to external systems: Slack, email, databases, APIs |
Define workflows in the dashboard or via the API. Each workflow has a trigger and one or more steps executed in sequence or parallel.
Step Types
| Step | Description |
|---|---|
| Parse | Run parsing and chunking on the document |
| Extract | Run extraction with a schema |
| Notify | Send email, Slack message, or webhook |
| Transform | Call external API or run custom logic |
Steps receive output from previous steps. For example, a parse step outputs document ID; an extract step uses that ID.
Triggers
| Trigger | Description |
|---|---|
| Upload | Fires when a document is uploaded to a folder or endpoint |
| Webhook | Fires when DocLD receives a webhook at your configured URL |
| Schedule | Fires on a cron schedule (e.g., daily batch) |
| Manual | Fires when you run the workflow manually |
Upload triggers are useful for "on upload, parse and extract." Webhook triggers integrate with external systems. Schedule triggers support batch processing.
Error Handling
Workflows run asynchronously. Failed steps can be configured to:
- Retry — Retry a step with exponential backoff
- Notify — Send alert on failure
- Continue — Skip failed step and continue (when applicable)
- Abort — Stop the workflow on failure
View execution history, logs, and retry failed runs from the dashboard. Job status tracks each step.
Use Cases
| Use Case | Trigger | Steps |
|---|---|---|
| Invoice pipeline | Upload to folder | Parse → Extract (Invoice schema) → Webhook to ERP |
| Batch extraction | Schedule (nightly) | Parse all new docs → Extract (Contract schema) → Notify |
| Document ready | Document processed | Webhook to downstream system |
| Manual review | Webhook | Extract → If low confidence, route to review queue |
Workflows can run extraction when a document reaches a certain status, send a webhook when processing completes, or schedule batch processing jobs.
Related Concepts
Workflows automate parsing and extraction. Webhooks can trigger workflows or be sent as steps. Jobs track async processing. The API can create and run workflows programmatically.