Skip to main content
Intakes provide automated document ingestion endpoints. Each intake defines a way for external systems to submit documents into a specific document store within a project, triggering processing pipelines automatically. Intakes page showing configured intake endpoints with names, target stores, and status

​
How Intakes Work

An intake creates an endpoint that external systems can send documents to. When a document arrives at an intake endpoint:
  1. The document is uploaded to the configured document store
  2. A document family is created for tracking
  3. Any configured processing pipelines are triggered automatically
Diagram or flow showing document submission through an intake to a document store and processing pipeline

​
Configuring an Intake

1

Create Intake

Click the add button on the Intakes page to create a new intake endpoint.
2

Configure Target

Select the project and document store where incoming documents should be stored.
3

Set Processing Options

Configure what happens when a document arrives, such as which assistant or pipeline should process it.
Intake configuration form showing target project, document store, and processing options
Each intake provides a unique URL and authentication credentials. Keep these secure, as anyone with the intake URL and credentials can submit documents to your organization.