List Liking Users
twitter.list_liking_users
ActionChat & messagingconnection required
Calls the X (Twitter) API with the connection's credentials.
One page of the users who liked a post.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- X (Twitter)
- Secret shape
- the X OAuth2 user-context access token, or {"access_token": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
6 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 |
|---|---|---|---|---|---|
tweet_id Numeric id of the post, e.g. the 'id' twitter.create_post emitted. Supports {{ }}. | string | Yes | — | — | 1460323737035677698 |
max_results Users per page, 1 to 100. | number | No | 100 | 1–100 | — |
pagination_token Cursor from a previous page's 'next_token'; leave blank for the first page. | string | No | — | — | — |
user_fields Comma-separated User fields to include, e.g. created_at,description,public_metrics. Without this X returns only id, name and username. | string | No | — | — | — |
expansions Comma-separated expansions to resolve into 'includes', e.g. author_id,attachments.media_keys. | string | No | — | — | — |
post_fields Comma-separated Post fields to include, e.g. created_at,public_metrics,author_id. Without this X returns only id and text. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"max_results": 100,
"tweet_id": "1460323737035677698"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
users The User objects on this page. | array | — |
count How many users this page carried. | number | — |
next_token Cursor for the next page; empty on the last one. | string | — |
result_count The result count X reported in meta. | number | — |
includes Objects pulled in by 'expansions' — users, media, polls, places. Empty when none asked for. | object | — |
{
"count": 0,
"includes": {},
"next_token": "",
"result_count": 0,
"users": []
}Notes
- X API access is tiered and metered: most read endpoints need a paid plan, and since 6 February 2026 new developers get pay-per-use credits rather than a free tier. A 403 here usually means the plan, not the code.
- The connection's access token must already carry the scopes this node needs; X does not grant them per call, so a missing scope is a 401 on every run.
- Needs the OAuth2 scopes like.read, tweet.read, users.read.
See List Liking Users run in a workflow.
In a technical demo we add the X (Twitter) connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.