GitHub

Manage repositories, issues, pull requests, and actions via the GitHub API.

Detail	Value
Category	Dev Tools
Base URL	https://api.github.com
Authentication	Bearer Token
Endpoints	7
Connector key	github

Using GitHub in a workflow

1. Go to Connections and click New Connection.
2. Pick GitHub from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /repos/{owner}/{repo}	Get a repository
GET /repos/{owner}/{repo}/issues	List repository issues
POST /repos/{owner}/{repo}/issues	Create an issue
GET /repos/{owner}/{repo}/pulls	List pull requests
POST /repos/{owner}/{repo}/pulls	Create a pull request
GET /repos/{owner}/{repo}/actions/runs	List workflow runs
GET /user/repos	List authenticated user repositories

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /repos/{owner}/{repo}

Get a repository

Detail	Value
Operation ID	devtools.getRepo
Method	GET
Path	/repos/{owner}/{repo}

Parameters

Name	Location	Type	Required
owner	path	string	Yes
repo	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.getRepo.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitHub API reference.

GET /repos/{owner}/{repo}/issues

List repository issues

Detail	Value
Operation ID	devtools.listIssues
Method	GET
Path	/repos/{owner}/{repo}/issues

Parameters

Name	Location	Type	Required
owner	path	string	Yes
repo	path	string	Yes
state	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listIssues.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitHub API reference.

POST /repos/{owner}/{repo}/issues

Create an issue

Detail	Value
Operation ID	devtools.createIssue
Method	POST
Path	/repos/{owner}/{repo}/issues

Parameters

Name	Location	Type	Required
owner	path	string	Yes
repo	path	string	Yes

Request Body

Field	Type
title	string
body	string
labels	array

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.createIssue.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitHub API reference.

GET /repos/{owner}/{repo}/pulls

List pull requests

Detail	Value
Operation ID	devtools.listPullRequests
Method	GET
Path	/repos/{owner}/{repo}/pulls

Parameters

Name	Location	Type	Required
owner	path	string	Yes
repo	path	string	Yes
state	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listPullRequests.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitHub API reference.

POST /repos/{owner}/{repo}/pulls

Create a pull request

Detail	Value
Operation ID	devtools.createPullRequest
Method	POST
Path	/repos/{owner}/{repo}/pulls

Parameters

Name	Location	Type	Required
owner	path	string	Yes
repo	path	string	Yes

Request Body

Field	Type
title	string
head	string
base	string
body	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.createPullRequest.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitHub API reference.

GET /repos/{owner}/{repo}/actions/runs

List workflow runs

Detail	Value
Operation ID	devtools.listWorkflowRuns
Method	GET
Path	/repos/{owner}/{repo}/actions/runs

Parameters

Name	Location	Type	Required
owner	path	string	Yes
repo	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listWorkflowRuns.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitHub API reference.

GET /user/repos

List authenticated user repositories

Detail	Value
Operation ID	devtools.listUserRepos
Method	GET
Path	/user/repos

Parameters

Name	Location	Type	Required
per_page	query	integer	No
sort	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listUserRepos.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitHub API reference.