---
title: "How to connect your GitHub open source product to MadKudu"
slug: "how-to-connect-your-github-open-source-product-to-madkudu"
updated: 2025-01-21T20:04:25Z
published: 2025-01-21T20:04:25Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.madkudu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to connect your GitHub open source product to MadKudu

## **GitHub Signals**

> [!NOTE]
> Who this article is for:
> 
> **Admins** managing integrations and tools for sales teams.

> [!NOTE]
> Availability
> 
> GitHub signals are a premium signals add-on.

#### Pre-requisites

- GitHub signals are part of a premium offer and must be enabled as part of your MadKudu subscription.
- You need admin access to the MadKudu console.
- No administrative access to your GitHub account is required, as MadKudu tracks public repositories only.

#### Step 1: Connect Your GitHub Repositories

![](https://cdn.document360.io/a55e7ea5-b8ac-4456-874d-10cc92097370/Images/Documentation/Screenshot 2024-11-27 at 12.08.12 PM(1).png)

1. Log into the MadKudu Admin console.
2. Navigate to **Integrations** and search for **GitHub**.
3. Enter your repositories:
  - For specific repositories, list them individually.
  - A common use-case is to **manually add the most starred / active repositories**so you don’t miss out on key activity.

MadKudu will begin syncing GitHub signals from your repositories. Note: Historical data sync may take a few hours.

![](https://cdn.document360.io/a55e7ea5-b8ac-4456-874d-10cc92097370/Images/Documentation/image(211).png)

#### Step 2: Refresh the event mapping for the changes to apply

To ensure GitHub events appear on Copilot, you must **refresh and publish**a new event mapping.

Follow these steps:

- Navigate to [https://app.madkudu.com/](https://app.madkudu.com/)
- Go to the Mapping section > Event mapping
- Click to edit any connected integration
- Start a new draft, but do not make any changes to the mapping
- Save the draft > Publish event mapping!

This process refreshes the GitHub signals and ensures they display correctly in Copilot.

![](https://cdn.document360.io/a55e7ea5-b8ac-4456-874d-10cc92097370/Images/Documentation/image(701).png)

#### Step 3: Add GitHub Playbooks to Your Teams’ Copilot Accounts

To enable your sales team to act on GitHub engagement signals:

1. Log into **Copilot** (installed in Salesforce or via the Chrome extension).
2. In the left navigation bar, click **+ New playbook**, then select **Playbook library**.
3. Choose the GitHub playbooks.
4. Assign a Gong/Outreach/Salesloft sequence to each playbook.
5. Adjust sharing settings to either the entire org or specific teams.
6. Click **Save playbooks**.

Your team is all set! They will start receiving new GitHub engagement records in their playbooks.

![](https://cdn.document360.io/a55e7ea5-b8ac-4456-874d-10cc92097370/Images/Documentation/Screenshot 2024-11-27 at 12.05.31 PM.png)

#### Troubleshooting and Support

If you encounter issues during setup, contact us at product@madkudu.com