Get User Settings History
gong.get_user_settings_history
ActionCRM & salesconnection required
Calls the Gong API with the connection's credentials.
List the recorded changes to one user's Gong settings over time.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Gong
- Secret shape
- {"username": "<access key>", "password": "<access key secret>"} — the access_key / access_key_secret spelling is accepted too
- Config it needs
- base_url, workspace_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 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 |
|---|---|---|---|---|---|
user_id Gong's numeric identifier for the user (up to 20 digits). | string | Yes | — | — | 234599484848423 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"user_id": "234599484848423"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The records on this page, each exactly as Gong returned it. | array | — |
count How many records this page holds. | number | — |
cursor Feed back as 'cursor' to fetch the next page; empty once the last page is reached. | string | — |
has_more True while Gong still has records beyond this page. | boolean | — |
total_records Records matching the request across every page. | number | — |
request_id Gong's reference id for this request, for support tickets. | string | — |
{
"count": 0,
"cursor": "",
"has_more": false,
"items": [],
"request_id": "",
"total_records": 0
}See Get User Settings History run in a workflow.
In a technical demo we add the Gong connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.