How to connect your GitHub open source product to MadKudu

  • Updated on Dec 16, 2024
  • Published on Oct 9, 2024
  • 1 minute(s) read

GitHub Signals

Who this article is for:

Admins managing integrations and tools for sales teams.

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

  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.

    • To track all repositories under your organization, enter {organization}/* (e.g., snyk/*).

  4. Click Save.

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

Step 2: 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.

Troubleshooting and Support

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