Will renaming a Busabase field break an n8n mapping?

Question

When submitting AI output from n8n to Busabase, should the mapping use a field ID or the field name shown in the UI?

For example, if “Customer name” becomes “Company name,” I'd want the workflow to keep writing to the same field. Beyond checking for a successful HTTP response, what's the easiest way to inspect the field values actually submitted in the change request? A minimal JSON example would help with wiring this up.

Kelly · Answer

Use the field's stable **slug** as the JSON key when n8n writes a [Busabase](https://busabase.com) record. The visible field name can change from “Customer name” to “Company name” while a slug such as customer_name stays the same. Neither the display label nor the field's internal ID is the key in a record payload. Recheck the mapping if someone deletes and recreates the field or changes the integration's actual slug.

For an update, POST /api/v1/records/{recordId}/change-requests with a body like this, replacing the record ID in the URL and the slug with your actual values:

```json
{"operation":"update","fields":{"customer_name":"Acme"},"message":"Update company name","autoMerge":false}
```

Save the returned Change Request ID. Open it in Inbox to compare before/after values, or GET /api/v1/change-requests/{changeRequestId} to inspect the submitted operation's field keys and values. A successful submission can still be awaiting review; test one record end to end before changing the n8n workflow.

Your reply