Create Thing
bubble.create_thing
ActionBusiness appsconnection required
Calls the Bubble API with the connection's credentials.
Create one record of a data type in the connection's Bubble app.
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
2 fields, 2 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 |
fields The Bubble field names and values to write, 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
}
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The unique id Bubble gave the new record. | string | — |
status Bubble's outcome for the create, normally 'success'. | string | — |
data_type The data type the record was created in. | string | — |
{
"data_type": "",
"id": "",
"status": ""
}Related Bubble nodes
See Create 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.