Pipelines & mappings#

A pipeline moves data from a source to a destination when its conditions are met.

Anatomy#

• Source entity — what the pipeline watches (e.g. Opportunity).
• Trigger conditions — when it fires. Conditions support equality, "changed", "changed to <value>", "is not null", and combine with AND.
• Steps — the ordered destination objects it writes, where a later step can reference an earlier one.
• Field maps — how each source field becomes a destination field, with an optional transform (constant, concatenation, date format, step reference).

Two kinds of pipeline#

• An ERP/destination pipeline maps source fields to destination object fields — the classic source → destination mapper with a source pane, a mapping center, and a destination pane.
• A workflow pipeline targets a workflow (like Deal Desk) instead of a destination system. It has no destination connection; its "mapping" is the set of deal fields shown on the approval card — a source path, a label, and an optional format. The pipeline editor shows a deal-fields editor for these.

Building a mapping#

In the console's pipeline editor, click a source field then a destination field to create a mapping. The editor validates as you go — flagging duplicate destinations, drifted fields, and unmapped required fields — and lets you test a pipeline against a real record (a dry run) or preview it against the most recent stored event without a round trip.