Upsert LarkBase records with n8n
Use a stable business ID and an explicit update-or-insert branch for reliable LarkBase writes.
TL;DR: An upsert needs a stable business ID and an explicit update/insert branch. LarkBase's record_id identifies a stored row; it is not always the business key used by an external system.
Find the record first
Search for the external business ID, then update the matching record_id. If no record exists, insert a new row and persist the returned record ID when the workflow needs it later. Do not match on a mutable customer name or display label.
Keep manually maintained columns separate from fields owned by automation. Validate required values before the write, batch requests within API limits, and make retries idempotent so duplicate deliveries cannot create duplicate rows.
Before production
Test insert, update, duplicate delivery, missing ID, changed schema, rate limiting and partial failure. Log the decision and response for each record, alert on ambiguous matches, and provide a safe replay procedure.