Modify Thing
bubble.modify_thing
ActionBusiness appsconnection required
Calls the Bubble API with the connection's credentials.
Change only the named fields on one record, leaving the rest alone.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Bubble
- Secret shape
- the API token, or {"api_token": "…"}
- Config it needs
- base_url, branch, test_data_type
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
data_type The Bubble data type to work with; Bubble addresses it lowercase with no spaces. | string | Yes | — | — | rentalunit |
thing_id The record's Bubble unique id, the '_id' field on the thing. | string | Yes | — | — | 1672398191097x872601726695236800 |
fields The Bubble field names and values to change, as a JSON object. | object | Yes | — | ≥ 1 characters | {"Unit name":"Rental unit 4","Unit number":4} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"data_type": "rentalunit",
"fields": {
"Unit name": "Rental unit 4",
"Unit number": 4
},
"thing_id": "1672398191097x872601726695236800"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
modified True once Bubble accepted the change. | boolean | — |
id The unique id of the record that was changed. | string | — |
data_type The data type the record belongs to. | string | — |
fields The field names that were sent in the change. | array | — |
{
"data_type": "",
"fields": [],
"id": "",
"modified": false
}Related Bubble nodes
See Modify Thing run in a workflow.
In a technical demo we add the Bubble connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.