Back to Integrations
integrationWebhook node
integrationGitHub node

Webhook and GitHub integration

Save yourself the work of writing custom integrations for Webhook and GitHub and use n8n instead. Build adaptable and scalable Development, and Core Nodes workflows that work with your technology stack. All within a building experience you will love.

How to connect Webhook and GitHub

  • Step 1: Create a new workflow
  • Step 2: Add and configure nodes
  • Step 3: Connect
  • Step 4: Customize and extend your integration
  • Step 5: Test and activate your workflow

Step 1: Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

Webhook and GitHub integration: Create a new workflow and add the first step

Step 2: Add and configure Webhook and GitHub nodes

You can find Webhook and GitHub in the nodes panel. Drag them onto your workflow canvas, selecting their actions. Click each node, choose a credential, and authenticate to grant n8n access. Configure Webhook and GitHub nodes one by one: input data on the left, parameters in the middle, and output data on the right.

Webhook and GitHub integration: Add and configure Webhook and GitHub nodes

Step 3: Connect Webhook and GitHub

A connection establishes a link between Webhook and GitHub (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

Webhook and GitHub integration: Connect Webhook and GitHub

Step 4: Customize and extend your Webhook and GitHub integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect Webhook and GitHub with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

Webhook and GitHub integration: Customize and extend your Webhook and GitHub integration

Step 5: Test and activate your Webhook and GitHub workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from Webhook to GitHub or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

Webhook and GitHub integration: Test and activate your Webhook and GitHub workflow

Sync Zendesk tickets with subsequent comments to GitHub issues

This workflow creates a GitHub issue when a new ticket is created in Zendesk. Subsequent comments on the ticket in Zendesk are added as comments to the issue in GitHub.

Prerequisites

Zendesk account and Zendesk credentials.
GitHub account and GitHub credentials.
GitHub repository to create issues in.

How it works

The workflow listens for new tickets in Zendesk.
When a new ticket is created, the workflow creates a new issue in GitHub.
The GitHub issue number is then saved in one of the ticket's fields (in setup we call this "GitHub Issue Number").
The next time a comment is added to the ticket, the workflow retrieves the GitHub issue number from the ticket's field and adds the comment to the issue in GitHub.

Setup

This workflow requires that you set up a webhook in Zendesk. To do so, follow the steps below:

In the workflow, open the On new Zendesk ticket node and copy the webhook URL.
In Zendesk, navigate to Admin Center > Apps and integrations > Webhooks > Actions > Create Webhook.
Add all the required details which can be retrieved from the On new Zendesk ticket node. The webhook URL gets added to the “Endpoint URL” field, and the “Request method” should match what is shown in n8n.
Save the webhook.
In Zendesk, navigate to Admin Center > Objects and rules > Business rules > Triggers > Add trigger.
Give trigger a name such as “New tickets”.
Under “Conditions” in “Meet ALL of the following conditions”, add “Status is New”.
Under “Actions”, select “Notify active webhook” and select the webhook you created previously.
In the JSON body, add the following:

    {
	"id": "{{ticket.id}}",
	"comment": "{{ticket.latest_comment_html}}"
}

Save the Zendesk trigger.

You will also need to set up a field in Zendesk to store the GitHub issue number. To do so, follow the steps below:

In Zendesk, navigate to Admin Center > Objects and rules > Tickets > Fields > Add field.
Use the number field option and give the field a name such as “GitHub Issue Number”.
Save the field.
In n8n, open the Update ticket node and select the field you created in Zendesk.

Nodes used in this workflow

Popular Webhook and GitHub workflows

🔄 Workflow Repos8r: Github Version Control User Interface for n8n Workflows

💪 How it works Seamlessly track, manage, and version-control your n8n workflows with an intuitive Git-style system. Whether you're making updates or creating new workflows, this tool ensures structured commits, detailed change tracking, and seamless GitHub integration—all within a Matrix-inspired UI. 🎯 Who is this for? Perfect for: n8n Developers & Automation Engineers** – Maintain workflow history and prevent accidental overwrites. Teams Collaborating on Automation** – Track and commit changes with structured version control. DevOps & IT Professionals** – Streamline deployment across multiple n8n environments. 🚀 Key Features Version Control & Workflow Management Commit changes when editing existing workflows Create & commit new workflows from scratch Detect modifications with deep node comparison Access repo with direct links from changes window Workflow JSON Browser Caching **to avoid large loads on n8n" Core Features Workflow Management Workflow Selection**: Easy selection of n8n workflows and GitHub workflows from dropdown menus Smart Caching**: Client-side caching of workflows for faster loading (1-week cache duration) Cache Control**: Manual cache clearing via hard refresh (Cmd+Shift+R) Matrix-Style UI**: Terminal-inspired interface with glowing effects and animations GitHub Integration Push to GitHub**: Direct pushing of n8n workflows to GitHub repositories Commit Control**: Automated commit message generation with workflow details Branch Management**: Automatic branch creation and management Pull from GitHub**: Future feature for pulling workflows from GitHub (Coming Soon) Workflow Comparison Side-by-Side Comparison**: Compare n8n workflows with their GitHub counterparts Change Detection**: Automatic detection and highlighting of workflow changes Diff Visualization**: Clear visualization of additions, deletions, and modifications JSON Validation**: Ensures workflow JSON integrity before operations User Experience System Notifications**: Matrix-themed toast notifications for important alerts 30-second duration with manual close option Context-aware messages (e.g., cache refresh hints) Glowing effects matching system console aesthetics Loading Animations**: Matrix-style loading indicators during operations Error Handling**: Clear error messages and recovery suggestions Responsive Design**: Adapts to different screen sizes Security & Performance Local Storage**: Efficient client-side storage for workflow data Header Authentication**: Secure API communication with authentication tokens Performance Optimization**: Smart caching to reduce server load Data Validation**: Input validation and sanitization Technical Features Code Organization Modular Structure**: Well-organized HTML, CSS, and JavaScript Component Separation**: Clear separation of concerns CSS Variables**: Consistent styling with CSS custom properties Event Handling**: Robust event listeners and handlers API Integration n8n Integration**: Direct communication with n8n workflow API GitHub API**: Seamless integration with GitHub repositories RESTful Endpoints**: Clean API design for workflow operations Error Handling**: Comprehensive error handling and user feedback Development Features Debug Mode**: Console logging for development Code Comments**: Well-documented code sections CSS Animations**: Smooth transitions and effects Browser Compatibility**: Works across modern browsers Future Enhancements Pull workflows from GitHub repositories Enhanced diff visualization Additional GitHub integration features Extended caching options More customization options for notifications Advanced workflow comparison tools GitHub Integration Push workflows directly to GitHub Commit new workflows directly to GitHub Auto-generate structured commit messages 🔴 (Coming Soon: Pull workflows from GitHub into n8n) Change Detection Identifies node additions, deletions, and property modifications Compares connections, settings, and configurations Real-time visualization** of detected changes Sleek UI for Effortless Control Matrix-style interface** for a futuristic feel Clear prompts to prevent accidental overwrites Interactive workflow commit & sync options 🔧 Setup & Usage Generate your n8n API key Set up GitHub repository & access tokens Create Generic Basic Auth credentials Create Generic Header Auth credentials Set the workflow variables Deploy & start tracking your workflow versions 📚 Use Cases 🔹 Workflow Development – Ensure clean versioning and commit history. 🔹 Team Collaboration – Review and track modifications before deployment. 🔹 Audit & Compliance – Maintain an organized change log. 🙌 Built for the n8n Community Created with ❤️ to bring reliable version control to the n8n community.

Sync Zendesk tickets with subsequent comments to GitHub issues

This workflow creates a GitHub issue when a new ticket is created in Zendesk. Subsequent comments on the ticket in Zendesk are added as comments to the issue in GitHub. Prerequisites Zendesk account and Zendesk credentials. GitHub account and GitHub credentials. GitHub repository to create issues in. How it works The workflow listens for new tickets in Zendesk. When a new ticket is created, the workflow creates a new issue in GitHub. The GitHub issue number is then saved in one of the ticket's fields (in setup we call this "GitHub Issue Number"). The next time a comment is added to the ticket, the workflow retrieves the GitHub issue number from the ticket's field and adds the comment to the issue in GitHub. Setup This workflow requires that you set up a webhook in Zendesk. To do so, follow the steps below: In the workflow, open the On new Zendesk ticket node and copy the webhook URL. In Zendesk, navigate to Admin Center > Apps and integrations > Webhooks > Actions > Create Webhook. Add all the required details which can be retrieved from the On new Zendesk ticket node. The webhook URL gets added to the “Endpoint URL” field, and the “Request method” should match what is shown in n8n. Save the webhook. In Zendesk, navigate to Admin Center > Objects and rules > Business rules > Triggers > Add trigger. Give trigger a name such as “New tickets”. Under “Conditions” in “Meet ALL of the following conditions”, add “Status is New”. Under “Actions”, select “Notify active webhook” and select the webhook you created previously. In the JSON body, add the following: { "id": "{{ticket.id}}", "comment": "{{ticket.latest_comment_html}}" } Save the Zendesk trigger. You will also need to set up a field in Zendesk to store the GitHub issue number. To do so, follow the steps below: In Zendesk, navigate to Admin Center > Objects and rules > Tickets > Fields > Add field. Use the number field option and give the field a name such as “GitHub Issue Number”. Save the field. In n8n, open the Update ticket node and select the field you created in Zendesk.

Build your own Webhook and GitHub integration

Create custom Webhook and GitHub workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

GitHub supported actions

Create
Create a new file in repository
Delete
Delete a file in repository
Edit
Edit a file in repository
Get
Get the data of a single file
List
List contents of a folder
Create
Create a new issue
Create Comment
Create a new comment on an issue
Edit
Edit an issue
Get
Get the data of a single issue
Lock
Lock an issue
Get Repositories
Returns all repositories of an organization
Create
Creates a new release
Delete
Delete a release
Get
Get a release
Get Many
Get many repository releases
Update
Update a release
Get
Get the data of a single repository
Get Issues
Returns issues of a repository
Get License
Returns the contents of the repository's license file, if one is detected
Get Profile
Get the community profile of a repository with metrics, health score, description, license, etc
Get Pull Requests
Returns pull requests of a repository
List Popular Paths
Get the top 10 popular content paths over the last 14 days
List Referrers
Get the top 10 referrering domains over the last 14 days
Create
Creates a new review
Get
Get a review for a pull request
Get Many
Get many reviews for a pull request
Update
Update a review
Get Repositories
Returns the repositories of a user
Invite
Invites a user to an organization
Disable
Disable a workflow
Dispatch
Dispatch a workflow event
Enable
Enable a workflow
Get
Get a workflow
Get Usage
Get the usage of a workflow
List
List workflows

Webhook and GitHub integration details

integrationWebhook node
Webhook

Webhooks are automatic notifications that apps send when something occurs. They are sent to a certain URL, which is effectively the app's phone number or address, and contain a message or payload. Polling is nearly never quicker than webhooks, and it takes less effort from you.

Use case

Save engineering resources

Reduce time spent on customer integrations, engineer faster POCs, keep your customer-specific functionality separate from product all without having to code.

Learn more

FAQs

  • Can Webhook connect with GitHub?

  • Can I use Webhook’s API with n8n?

  • Can I use GitHub’s API with n8n?

  • Is n8n secure for integrating Webhook and GitHub?

  • How to get started with Webhook and GitHub integration in n8n.io?

Need help setting up your Webhook and GitHub integration?

Discover our latest community's recommendations and join the discussions about Webhook and GitHub integration.
Benjamin Hatton
Albert Ashkhatoyan
Víctor González
Salomão
sg tech

Looking to integrate Webhook and GitHub in your company?

Over 3000 companies switch to n8n every single week

Why use n8n to integrate Webhook with GitHub

Build complex workflows, really fast

Build complex workflows, really fast

Handle branching, merging and iteration easily.
Pause your workflow to wait for external events.

Code when you need it, UI when you don't

Simple debugging

Your data is displayed alongside your settings, making edge cases easy to track down.

Use templates to get started fast

Use 1000+ workflow templates available from our core team and our community.

Reuse your work

Copy and paste, easily import and export workflows.

Implement complex processes faster with n8n

red iconyellow iconred iconyellow icon