Entity Enricher Trigger icon

Entity Enricher Trigger

Fires on Entity Enricher enrichment events and database deltas

Entity Enricher Trigger

AI-generated

Summary

Trigger workflows upon events from the Entity Enricher service related to schema enrichment results, rejected enrichments, or database change deltas.

Inputs

  • Authentication: choose between API Key or OAuth2 authentication methods to connect to the Entity Enricher service. (required) — Select the authentication method to use for connecting to the Entity Enricher API.
  • Event: select the type of event to listen for, either enrichment result, rejected enrichments for database save, or availability of database deltas. (required) — The event that will cause the trigger to fire in the workflow.
  • Schema Name or ID: required when the event is enrichment result or rejected, selects the schema whose events this trigger listens to. (required) — The schema ID or name whose enrichment events will cause the trigger to fire. Choose from the loaded schemas or provide an expression.
  • Database Sync ID: required when the event is database deltas available, specifies which database sync's changes will generate trigger events. (required) — The database synchronization identifier whose delta events will cause the trigger to fire.
  • Fetch Deltas on Fire: optional boolean for delta_available event; when enabled, the node fetches and leases pending deltas upon trigger fire, emitting one item per delta; if disabled, it emits only the notification without deltas. — Determines whether to retrieve database deltas immediately when the trigger fires.
  • Schema (Multi-Schema Databases) Name or ID: optional for delta_available event; selects the linked schema whose webhook to register in multi-schema databases; if left empty for single-schema databases. — For multi-schema databases, select which linked schema this trigger subscribes to; each linked schema drives its own webhook and workflow.

Output shape

one or more items emitted per trigger firing, each containing JSON data for an event: enrichment result data or rejected enrichment data for the first two event types, or database delta records (each with additional metadata) for the delta_available event.

For enrichment_result and rejected_for_database_save events, the trigger auto-registers a schema-level webhook that fires once per enrichment event with the event data. For delta_available events, the trigger registers a webhook per linked schema; on firing, if fetchOnFire is true, it fetches and leases the pending SQL deltas from the specified database sync, emitting one item per delta. The workflow should perform an explicit acknowledgment operation to confirm processing of database deltas. The node supports both API Key and OAuth2 authentication.

Examples

Example 1: Trigger on successful enrichment results for a specified schema

Set Event to 'Enrichment Result' and choose the appropriate Schema Name or ID to listen for enrichment completions; authenticate via API Key or OAuth2.

Example 2: Trigger on database change deltas availability

Set Event to 'Database Deltas Available', specify the Database Sync ID, optionally set 'Fetch Deltas on Fire' to control immediate retrieval, and select a linked schema if the database supports multiple schemas.

Links

Discussion