Actions18
- Attachment Actions
- Configuration Actions
- Database Sync Actions
- Enrichment Actions
- Fusion Actions
- Record Actions
- Schema Actions
Enrichment → Enrich Entity
AI-generatedSummary
Enriches one input entity using the organization’s automatically selected best model and strategy, then returns the enriched data. Choose a target schema and optionally provide language preferences, web search, or binary files as source material.
Inputs
- Authentication (required) — Connect with an API key (the default) or OAuth2 credentials.
- Schema Name or ID (required) — Select the schema that defines the enrichment output structure.
- Input item JSON (required) — The entity data comes from each input item's JSON. Empty input is rejected; its field names do not need to match the schema.
- Upload Input Binary Files — Off by default. When enabled, uploads every binary file on the input item and uses them as source material. At least one binary file must be present.
- Language Names or IDs — Languages for multilingual fields; defaults to English.
- Web Search Name or ID — Off by default. Enable provider web search for the automatically selected model when supported.
Output shape
One output item containing the enriched entity's JSON fields.
The operation uses the organization’s best model and automatic strategy; model selection and enrichment metadata are not exposed in this simple operation. If binary upload is enabled, uploaded attachments are deleted after enrichment, including when enrichment fails. A timeout or classification pause can cancel the job and fail the operation.