GitHub API Request node

Free-form request to the GitHub API for anything the other GitHub blocks don't cover. Uses your connected account, only paths under api.github.com. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

8 min readUpdated September 10, 2026

What this node does

Free-form request to the GitHub API for anything the other GitHub blocks don't cover. Uses your connected account, only paths under api.github.com.

Use GitHub API Request as a clearly defined step in an anymize workflow.

Processes one input.
Provides one output for following steps.
Runs as a regular step in the flow.

Set up the node

01Open a workflow and add GitHub API Request from the node catalog.
02If your GitHub account is not connected yet, connect it right in the node panel or under Connectors.
03Complete the required fields and map values from previous steps.
04Run the node with a small test record and inspect its output.
05Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Choose the required function in Action. The panel then shows the relevant settings.

Fetch data (GET)
Change data

Settings

Field	Meaning	Area
Action	Choices: Fetch data (GET), Change data	Standard
Path	GitHub API path, starting with /, e.g. /repos/octocat/hello-world/issues.	Standard
Query parameters	Appended as ?key=value.	Standard
Method	Choices: POST (create), PUT (set), PATCH (change), DELETE (delete)	Standard
Body (JSON)	The JSON body of the request.	Standard
GitHub account	Leave empty and the step uses your connected GitHub account.	Standard
Run once per item	Off (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry.	Standard
If one item fails	"Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file.	Standard
Pause between items (milliseconds)	Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes).	Standard

Inputs and outputs

Input	Meaning	Type
Standard	Receives the complete result from the previous step.	JSON

Output	Meaning	Type
Standard	Makes the result available to the next step as JSON.	JSON

This node can process lists item by item. Error handling and the delay between items are available in advanced settings.

Example and test run

Get your own account: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "path": "/user"
}

Access and security

The node works with your own connected GitHub account. It only sees and changes what this account is allowed to. Check the permissions shown when you connect. The matching area (Issues, Pull Requests, Repos) must also be switched on in the settings of your GitHub connection under Connectors. All areas are on by default.

"Allowed actions" in the settings of your GitHub connection under Connectors also applies to this node and is checked on every run. With "Read only" or "Read and draft", only the read actions run: Fetch data (GET). These actions need "Allow changes": Change data.

Keys and credentials belong in Workflow Secrets or your connected accounts. Never paste them as plain text into workflow fields, test data or descriptions.

Troubleshooting

No output: inspect the latest run and confirm that the previous node returned the expected fields.
Empty variable: open the previous step output and use a field name from the real test data.
Connection rejected: reconnect the service and grant the permissions required by this step.
Action blocked: set "Allowed actions" of the connection under Connectors to "Allow changes", or pick a read action.
List processed once: enable per-item execution in advanced settings.