Get Clicks Over Time
bitly.get_clicks
ActionBusiness appsconnection required
Calls the Bitly API with the connection's credentials.
Return the click count for one Bitlink per time bucket, so a workflow can chart or threshold the series.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Bitly
- Secret shape
- {"access_token": "…"} — a Bitly generic access token, or {"client_id": "…", "client_secret": "…", "refresh_token": "…"}
- Config it needs
- group_guid, domain, organization_guid
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 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 |
|---|---|---|---|---|---|
bitlink The Bitlink to act on, as domain/hash (bit.ly/2kZDMbT) or the full short URL. | string | Yes | — | — | bit.ly/2kZDMbT |
unit The size of one time bucket in the returned series. | string | No | day | one of "minute", "hour", "day", "week", "month" | — |
units How many of those units to look back over; -1 covers the whole history. | number | No | -1 | ≥ -1 | — |
unit_reference ISO-8601 timestamp of the most recent point to pull metrics for; defaults to now. | string | No | — | iso8601 format | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"bitlink": "bit.ly/2kZDMbT",
"unit": "day",
"units": -1
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
link_clicks One row per bucket, each with 'date' and 'clicks'. | array | — |
count How many buckets the series carried. | number | — |
unit The time bucket each row covers. | string | — |
units How many units the window spanned. | number | — |
unit_reference The most recent point in the window. | string | — |
bitlink The Bitlink the series belongs to. | string | — |
{
"bitlink": "",
"count": 0,
"link_clicks": [],
"unit": "",
"unit_reference": "",
"units": 0
}See Get Clicks Over Time run in a workflow.
In a technical demo we add the Bitly connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.