Source mappings

Turn inconsistent source labels into one canonical tag that routing can trust, so the same business meaning routes the same way everywhere.

Why it matters

Different webhook and email sources rarely agree on wording. Source mappings absorb those naming differences up front, so a small label change at the source never fragments how a lead is routed.

See it in HoneyFalcon

Step 1 of 3: source field and source value picker.

Step 2 of 3: mapping editor with canonical tag.

Step 3 of 3: active source field and value mapped to the target tag.

Normalize incoming labels into routing meaning

Map a source label to a canonical tag

A mapping connects the exact incoming source field and value to the tag you want routing to use. The source side matches what the sender actually writes; the canonical side carries the routing meaning.

Because the canonical value is derived and held consistent, two sources that spell the same intent differently still resolve to one tag.

Keep routing consistent across sources

Once mapped, every expected incoming webhook or email value resolves to the intended active tag, so equivalent leads route consistently across those automated sources.

You extend coverage by adding a mapping for each new label a source introduces, without touching the routing rules themselves.

Your mappings are ready when

• Every expected incoming value resolves to the intended active tag.
• A new source label is absorbed by adding one mapping, not by rewriting routing rules.

Continue learning

• Start from: For operations — start here
• Previous: Tag routing
• Next: Agent costs and rules