Overview

Processors transform records in-flight between extraction and sinking. Each processor receives a record, modifies the entity, and passes it on. Edges pass through unchanged.

Processors run sequentially in recipe order — the output of one becomes the input of the next:

processors:
  - name: enrich
    config:
      attributes:
        domain: payments
  - name: labels
    config:
      labels:
        source: meteor

If a processor fails, the whole run stops and fails. Processors are not retried.

Supported processors

For how the pipeline runs processors, see Architecture. For script examples, see the scripting guide.