List Team Members
github.list_team_members
ActionBusiness appsconnection required
Calls the GitHub API GET /orgs/{org}/teams/{team_slug}/members.
List the members of one team in an organisation.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- GitHub
- Secret shape
- the GitHub personal access token
- Resolved by
- config.connection_id, else node.connection_id, else the tenant's sole GitHub connection
Configuration
4 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 |
|---|---|---|---|---|---|
org Organisation login, e.g. coax. | string | Yes | — | — | github |
team_slug Team slug — the lowercased, hyphenated form of the team name. | string | Yes | — | — | core-team |
role Only maintainers, only members, or both. | string | No | all | one of "all", "member", "maintainer" | — |
max_items Stop after this many rows; further pages are followed via the Link header. | number | No | 100 | 1–1000 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"max_items": 100,
"org": "github",
"role": "all",
"team_slug": "core-team"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
members The members this step read. | array | — |
members[].login GitHub username. | string | — |
members[].id GitHub's internal user id. | number | — |
members[].type User or Bot. | string | — |
members[].html_url Link to the profile. | string | — |
count How many rows this step returned. | number | — |
{
"count": 0,
"members": [
{
"html_url": "",
"id": 0,
"login": "",
"type": ""
}
]
}Solutions with GitHub
See List Team Members run in a workflow.
In a technical demo we add the GitHub connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.