List Organisation Teams

github.list_org_teams

ActionBusiness appsconnection required

Calls the GitHub API GET /orgs/{org}/teams.

List the teams in a GitHub organisation.

Ask about GitHub All GitHub nodes Provider API docs ↗

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

2 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
org Organisation login, e.g. coax.	string	Yes	—	—	github
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"
}

Output

One shape.

result

Field	Type	Example
teams The teams this step read.	array	—
teams[].id Team id.	number	—
teams[].name Team display name.	string	—
teams[].slug Team slug — what the team endpoints take.	string	—
teams[].description Team description.	string	—
teams[].privacy closed or secret.	string	—
teams[].permission Default repository permission for the team.	string	—
teams[].html_url Link to the team.	string	—
count How many rows this step returned.	number	—

{
  "count": 0,
  "teams": [
    {
      "description": "",
      "html_url": "",
      "id": 0,
      "name": "",
      "permission": "",
      "privacy": "",
      "slug": ""
    }
  ]
}

Notes

The token must be an organisation member; teams are never public.

Related GitHub nodes

Solutions with GitHub

See List Organisation Teams 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.

Book a technical demo Talk to sales