GitHub automation hub: complete API controls for AI agents
Ready for 3.0What this workflow does
This AI workflow has 47 nodes and runs when an MCP client calls one of its tools. Along the way it connects GitHub and HTTP Request.
How it runs
Trigger: When an MCP client calls one of its tools.
- Get Repo (Github Tool): uses Github Tool
- Get Pull Requests (Github Tool): uses Github Tool
- Get Issues (Github Tool): uses Github Tool
- List Popular Paths (Github Tool): uses Github Tool
- Get License (Github Tool): uses Github Tool
- List Referrers (Github Tool): uses Github Tool
- Get Profile (Github Tool): uses Github Tool
- Custom POST Github Request (Http Request Tool): calls an HTTP API
- Custom GET Github Request (Http Request Tool): calls an HTTP API
- Custom PATCH Github Request (Http Request Tool): calls an HTTP API
…plus 2 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (3)
- Github Tool
n8n-nodes-base.githubTool - MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger - Http Request Tool
n8n-nodes-base.httpRequestTool
From the author
Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator? Join the community Quick Setup Guide: 1️⃣ Import this template into your n8n instance. 2️⃣ Configure GitHub credentials for the nodes. 3️⃣…