Sources & posting URLs
Give each supplier its own posting URL, and map the field names they send to the fields your pipeline expects.
A source is one supplier feeding one pipeline. Each source has its own posting URL and its own field mapping:
Find them on the pipeline canvas: click the Intake node, then click a source to open it. Every pipeline starts with one source named Default; Add a source creates another (rename it to the supplier's name — that's how leads are attributed).
The key in the URL is the authentication — no header, no separate API key. Full request/response details: Webhook API reference.
Field mapping
Each source keeps its own map of what they send → what your pipeline calls it.
| Row shows | Meaning |
|---|---|
email_address → email | Renamed on arrival. |
phone → phone with an auto tag | The name already matches one of your fields exactly. |
utm_term → — ignore (don't import) — | Dropped at intake, never stored on the lead. |
| A row with a warning border | Never decided. The field still arrives, under its own name. |
Fields are discovered automatically: every key a source posts is remembered and gets a row the next time you open it. You can also type a field name in the box at the bottom and add it before the first lead ever arrives. Removing a row is temporary — the field reappears if a future lead posts it.
Undecided fields are counted for you: the source list shows ⚠ N to map, and the source editor shows ⚠ N unmapped. It's a to-do list, not an error — those leads were accepted. Map them or mark them ignored to clear the counter.
Save with Save source. Mappings apply to leads arriving after the save.
Why one URL per supplier
- Attribution. You can see which supplier sent which lead, and cut one off without touching the others.
- Isolation. One supplier's odd field names (
Phone1,E-Mail) are mapped in their source only. - Rotation. Regenerate key on a leaked URL kills that URL alone. Give the supplier the new one first — the old one starts returning
401immediately. - Clean shutdown. Delete source stops that URL for good; posts to it are rejected.
Common questions
Do all my suppliers have to use different URLs? No, but you lose attribution and per-supplier mapping if they share one. Adding a source takes seconds.
A supplier sends fields I don't want. What do I do? Set them to ignore in the mapping. They're dropped at intake and never stored on the lead.
Do CSV imports and manual leads belong to a source? No. Those are one-time entries — the links are at the bottom of the Intake panel. See CSV import and manual entry.
A supplier added a new field. Do I have to tell them to stop? No. The new field arrives, is stored on the lead, and shows up in the mapping list flagged as unmapped so you can decide what it is.
Can two sources map different names onto the same field?
Yes — that's the point. email_address from one and Email from another can both land on email.