Update Datapoint
beeminder.update_datapoint
ActionBusiness appsconnection required
Calls the Beeminder API with the connection's credentials.
Change the value, timestamp or comment of one existing datapoint.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Beeminder
- Secret shape
- the personal auth token, or {"auth_token": "…"} / {"access_token": "…"}
- Config it needs
- username
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 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 |
|---|---|---|---|---|---|
goal The goal's slug — the last segment of its Beeminder URL, e.g. 'weight'. | string | Yes | — | — | weight |
datapoint_id The id of the datapoint to act on, as returned by a create or list call. | string | Yes | — | — | 5016fa9adad11576ad00000f |
value The new number to record. Decimals and negative numbers are both accepted; leave empty to keep the current value. | string | No | — | — | 220.6 |
timestamp Unix time in seconds that the datapoint belongs to; defaults to now. | number | No | — | ≥ 0 | 1325523600 |
comment A free-text note stored alongside the datapoint and shown on the graph page. | string | No | — | — | — |
- At least one of value, timestamp, comment must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"datapoint_id": "5016fa9adad11576ad00000f",
"goal": "weight",
"timestamp": 1325523600,
"value": "220.6"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id Unique id of the datapoint, used to edit or delete it. | string | — |
timestamp Unix time in seconds that the datapoint belongs to. | number | — |
daystamp The datapoint's date as YYYYMMDD, e.g. '20150831'. | string | — |
value The value recorded for that day. | number | — |
comment The note stored with the datapoint, empty when none. | string | — |
updated_at Unix time the datapoint was entered or last changed. | number | — |
requestid The idempotency key sent with the datapoint, echoed back. | string | — |
origin Where the datapoint came from, e.g. 'web' or an integration. | string | — |
creator The member who added it, or null when there is no logical one. | string | — |
is_dummy True for a datapoint Beeminder added itself, e.g. a derail. | boolean | — |
is_initial True for the datapoint added when the goal was created. | boolean | — |
created_at Unix time the datapoint row itself was created. | number | — |
{
"comment": "",
"created_at": 0,
"creator": "",
"daystamp": "",
"id": "",
"is_dummy": false,
"is_initial": false,
"origin": "",
"requestid": "",
"timestamp": 0,
"updated_at": 0,
"value": 0
}See Update Datapoint run in a workflow.
In a technical demo we add the Beeminder connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.