Production use of this feature is available for specific editions only. Contact our sales team for more information.
Use case
This component can be used to extract data for a range of purposes. For example, it is useful in industries such as finance, logistics, and healthcare, where documents like invoices, contracts, and patient records are often available in different formats, including PDFs and scanned images.Video example
Prerequisites
- Files you wish to process must be in your Snowflake stage.
- You must have created and configured a Document AI build model in Snowflake already. For more information, read Set up the required objects and privileges.
- The Document AI Predict component requires that your file’s relative path and presigned URL be available in a Snowflake table. Use this example query to populate your table:
The final step in the Snowflake tutorial, Create a document processing pipeline, isn’t required in .
Properties
A human-readable name for the component.
The Snowflake source database. The special value
[Environment Default] uses the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.The Snowflake source schema. The special value
[Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.The build name of the Document AI model. Read Prepare a Document AI model build to learn more.
Optionally specify the version of the model to use. If not set, this parameter will default to the latest version.
The source column containing the presigned URLs of the staged files the model should act on.Presigned URLs let the user bypass the authentication and sign-in process.As part of the Document AI API, provide a presigned URL to the document you want to run the model against. Document AI then uses the presigned URL to fetch the intended document.
- Yes: Outputs both your source URL columns and the prediction columns. This is the default setting.
- No: Only includes the new prediction columns.

