The bulk-upsert workflow node gets two new mappable fields that build relationships between your CRM records: link a client to its company, or a company to its tenant, using the parent's external ID from your source data.
Until now, external IDs on bulk upsert were only good for matching a row to itself — there was no way to say "this client belongs to the company with external ID X". If your source system already knows the hierarchy, you can now sync it directly instead of relying on email-domain guessing.
How it behaves
- Links are written on both inserts and updates, so a re-sync corrects a stale link automatically.
- A blank or unmapped value leaves the existing link alone — a partial source can never unlink records you've already connected.
- If a referenced parent doesn't exist, the row is counted as invalid with a clear reason in the node output, rather than silently creating an orphan. Sync parents before children.
- When you link clients to companies explicitly, the explicit mapping always wins — the automatic email-domain matching skips any row you've already settled.
Resolution runs in efficient batches, so large syncs stay fast. Available now on every bulk-upsert node — map the new fields in the node's configuration.