GitHub Actions

Manage workflows, trigger runs, and retrieve artifacts with GitHub Actions.

Detail	Value
Category	CI/CD
Base URL	https://api.github.com
Authentication	Bearer Token
Endpoints	8
Connector key	github-actions

Using GitHub Actions in a workflow

1. Go to Connections and click New Connection.
2. Pick GitHub Actions 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}/actions/workflows	List workflows
POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches	Trigger a workflow
GET /repos/{owner}/{repo}/actions/runs	List workflow runs
GET /repos/{owner}/{repo}/actions/runs/{run_id}	Get workflow run details
POST /repos/{owner}/{repo}/actions/runs/{run_id}/cancel	Cancel a workflow run
POST /repos/{owner}/{repo}/actions/runs/{run_id}/rerun	Rerun a workflow run
GET /repos/{owner}/{repo}/actions/runs/{run_id}/jobs	List jobs for a run
GET /repos/{owner}/{repo}/actions/runs/{run_id}/artifacts	List artifacts

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

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

List workflows

Detail	Value
Operation ID	cicd.listWorkflows
Method	GET
Path	/repos/{owner}/{repo}/actions/workflows

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub Actions connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.listWorkflows.
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 Actions API reference.

POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches

Trigger a workflow

Detail	Value
Operation ID	cicd.createWorkflowDispatch
Method	POST
Path	/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub Actions connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.createWorkflowDispatch.
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 Actions API reference.

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

List workflow runs

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

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub Actions connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.listWorkflowRuns.
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 Actions API reference.

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

Get workflow run details

Detail	Value
Operation ID	cicd.getWorkflowRun
Method	GET
Path	/repos/{owner}/{repo}/actions/runs/{run_id}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub Actions connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.getWorkflowRun.
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 Actions API reference.

POST /repos/{owner}/{repo}/actions/runs/{run_id}/cancel

Cancel a workflow run

Detail	Value
Operation ID	cicd.cancelWorkflowRun
Method	POST
Path	/repos/{owner}/{repo}/actions/runs/{run_id}/cancel

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub Actions connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.cancelWorkflowRun.
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 Actions API reference.

POST /repos/{owner}/{repo}/actions/runs/{run_id}/rerun

Rerun a workflow run

Detail	Value
Operation ID	cicd.rerunWorkflowRun
Method	POST
Path	/repos/{owner}/{repo}/actions/runs/{run_id}/rerun

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub Actions connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.rerunWorkflowRun.
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 Actions API reference.

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

List jobs for a run

Detail	Value
Operation ID	cicd.listJobsForWorkflowRun
Method	GET
Path	/repos/{owner}/{repo}/actions/runs/{run_id}/jobs

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub Actions connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.listJobsForWorkflowRun.
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 Actions API reference.

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

List artifacts

Detail	Value
Operation ID	cicd.listWorkflowRunArtifacts
Method	GET
Path	/repos/{owner}/{repo}/actions/runs/{run_id}/artifacts

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitHub Actions connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.listWorkflowRunArtifacts.
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 Actions API reference.