GitHub and Pingdom Integration
Connect GitHub and Pingdom to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about GitHub and Pingdom
Detailed info you need to know about GitHub and Pingdom integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect GitHub to Pingdom
Set up your GitHub and Pingdom integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect GitHub and Pingdom
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected GitHub and Pingdom nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between GitHub and Pingdom. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between GitHub and Pingdom work in WEXTL?
WEXTL exposes actions and triggers for GitHub and Pingdom that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
GitHub triggersPingdom actions
GitHub modules
- Accept a Repository Invitation Accepts a pending repository invitation so that you become a collaborator on that repository and gain its access.
- Add a Dependency an Issue Is Blocked by Marks an issue as blocked by another issue, so the blocker is recorded as a dependency.
- Add a Field to a User Owned Project Builds a field on a project owned by a user. Supply Single Select Options for a single select, or Iteration Configuration to add dated iterations.
- Add a Field to an Organization-owned Project Attaches a custom field to a project owned by an organization. Provide Single Select Options for a single select field, or an Iteration Configuration for an iteration field.
- Add a Repository Collaborator Invites a user to collaborate on a repository, with Permission as the access level, which only applies to organization-owned repositories. The invitation shows its Invitee and Inviter.
- Add a Repository to a Self-hosted Runner Group in an Organization Lets one more repository use the runners grouped under a self-hosted runner group owned by your organization.
- Add a Selected Repository to a Dependabot Organization Secret Gives one more repository access to a Dependabot secret of an organization, widening the selected repositories list.
- Add a Selected Repository to an Organization Actions Secret Grants an additional repository access to an organization Actions secret that is shared with selected repositories.
- Add a Selected Repository to an Organization Variable Lets one further repository access an organization variable whose audience is a list of selected repositories.
- Add a Selected Repository to the List of Repositories Allowed to Use Self-hosted Runners in an Organization Puts a repository on the allow list for self-hosted runners within your organization, letting that repository use the machines.
- Add a Self-hosted Runner to a Group for an Organization Puts a runner into a runner group, which makes the access rules of that group apply to it.
- Add a Sub-issue to an Issue Adds an existing issue as a sub-issue of a parent issue. Turn on Replace Parent to replace the current parent of the sub-issue.
- Add an Email Address for the Authenticated User Attaches one or more Emails to the GitHub account behind your credential.
- Add an Item to a User Owned Project Inserts an item into a project owned by a user, with the ID, Node ID and Content of the new item in the response.
- Add an Item to an Organization Owned Project Puts an item onto a project owned by an organization. The response shows its Content Type, Creator and Created At.
- Add App Access Restrictions Gives GitHub Apps push access to a protected branch. Use Apps to list them by slugified app name.
- Add Assignees to an Issue Assigns users to an issue by login and returns the updated issue.
- Add Custom Labels to a Self-hosted Runner for a Repository Gives a runner registered on one repository more Labels. The runner then carries its updated label list, which is returned.
- Add Custom Labels to a Self-hosted Runner for an Organization Attaches extra Labels to a runner registered with your organization. The complete label list of the runner is returned.
- Add Issue Field Values to an Issue Fills in organization issue fields on an issue by pairing each Field ID with a Value.
- Add Labels to an Issue Attaches new labels by name next to the labels an issue already carries.
- Add or Update Team Membership for a User Puts a user on an organization team or changes their existing membership, including their Role in the team.
- Add or Update Team Repository Permissions Gives a team access to a repository, or changes the access it already has. Use Permission to set a role such as pull, push or admin.
- Add Pull Requests to a Pull Request Stack Stacks more pull requests onto the top of an existing stack, taking them in the order of Pull Requests.
- Add Social Accounts for the Authenticated User Links one or more social media profiles to your own GitHub account.
- Add Status Check Contexts Makes more status checks mandatory before merging into a branch with protection.
- Add Team Access Restrictions Gives teams access to a protected branch, matched by slug. The response lists the teams that now have access.
- Add User Access Restrictions Includes individual users in the access list of a protected branch, by username, and lists everyone who has access.
- Approve a Workflow Run for a Fork Pull Request Approves a workflow run started by a pull request from a fork, letting the run proceed and its jobs start.
- Approve an Issue Suggestion Approves a suggestion on an issue so the proposed change takes effect.
- Block a User Blocks a GitHub user from your account, adding them to your blocked users.
- Block a User from an Organization Blocks a GitHub account from an organization and records it on the organization block list.
- Bulk Create Organization Custom Patterns Registers several custom secret scanning patterns for an organization together. Output has the Created Patterns.
- Bulk Create Repository Custom Patterns Adds several custom secret scanning patterns to a single repository at once, each with a Name, Pattern and delimiter or match rules.
- Bulk Delete Organization Custom Patterns Deletes several custom secret scanning patterns from an organization at once. Use Post Delete Action to choose what happens to alerts tied to them.
- Bulk Delete Repository Custom Patterns Deletes a group of custom secret scanning patterns from a repository. Set Post Delete Action to decide what becomes of alerts raised by those patterns.
- Cancel a GitHub Pages Deployment Stops a GitHub Pages deployment. A commit SHA of the deployment works in place of its Pages Deployment ID.
- Cancel a Workflow Run Interrupts a workflow run of a repository before it finishes.
- Cancel an Organization Invitation Cancels an invitation sent to someone for joining an organization.
- Check If a Gist Is Starred Checks whether your GitHub account has starred a particular gist, answering for its Gist ID.
- Check If a Person Is Followed by the Authenticated User Tells whether you follow a given GitHub account.
- Check If a Pull Request Has Been Merged Tells you whether a pull request has already landed in its base branch.
- Check If a Repository Is Starred by the Authenticated User Checks if the account behind your credential has put a star on the repository in question.
- Check If a User Can Be Assigned Tests whether a GitHub login is eligible to take issues in a repository.
- Check If a User Can Be Assigned to an Issue Asks whether a GitHub login may take on one particular issue of a repository.
- Check If a User Follows Another User Checks whether one GitHub account is among the people another account follows.
- Check If a User Is a Repository Collaborator Answers whether a user collaborates on a repository, based on their Username.
- Check If a User Is Blocked by an Organization Tests if a user shows up on the block list kept by an organization.
- Check If a User Is Blocked by the Authenticated User Checks whether you have a given GitHub account among your blocked users.
- Check If Dependabot Security Updates Are Enabled for a Repository Reports whether Dependabot security updates are switched on for a repository, with separate Enabled and Paused values.
Pingdom modules
- Create a Check Starts monitoring a Host with a chosen Check Type and Name. Add Check Interval (Minutes), Probe Regions or Response Time Threshold (ms) to tune the runs, and Contacts To Alert or Teams To Alert to notify people.
- Create a Maintenance Window Plans a quiet period with a Description, Start and End, during which chosen Uptime Checks or Transaction Checks are not alerted. Repeat, Repeat Every and Repeat Until make it recur.
- Create a Transaction Check Sets up a scripted browser check from a Name and the Steps to run. Add Region, Interval (Minutes) and Alert After Failed Tests to decide where, how often and when it alerts.
- Create an Alerting Contact Adds a person to notify about check problems. Add Email Targets and SMS Targets for where alerts reach them, or turn on Paused to hold notifications.
- Create an Alerting Team Groups people into a team under a Name, built from a list of Members.
- Delete a Check Deletes an uptime check along with all data collected for it. This cannot be undone.
- Delete a Maintenance Occurrence Removes one scheduled slot that belongs to a maintenance window.
- Delete a Maintenance Window Cancels planned downtime by deleting a maintenance window from the account.
- Delete a Transaction Check Deletes a scripted transaction check from the account.
- Delete an Alerting Contact Deletes a person who is notified about check problems.
- Delete an Alerting Team Removes a group of alert recipients from the account.
- Delete Multiple Checks Removes a batch of uptime checks with one request.
- Delete Multiple Maintenance Occurrences Deletes a batch of downtime slots with a single request.
- Delete Multiple Maintenance Windows Removes several maintenance windows at once.
- Get a Check Reads an uptime check with its Hostname, Status and Resolution. Turn on Include Teams to add the alerting teams.
- Get a Maintenance Occurrence Reads one occurrence of a maintenance window, showing its start (From) and end (To).
- Get a Maintenance Window Shows a maintenance window with its Description, Recurrencetype and Repeatevery.
- Get a Performance Summary Reads the response times of a check, one entry per interval of the chosen Resolution. Turn on Include Uptime to add uptime and downtime to each interval.
- Get a Root Cause Analysis Reads one root cause analysis of an outage for a check. Analysis IDs come from List Root Cause Analyses.
- Get a Transaction Check Fetches a transaction check with its Active flag, Interval and timestamps. Turn on Include Extended Tags for tag details.
- Get a Transaction Check Status Report Shows the States of a transaction check for the period from From to To, sorted by Order.
- Get a Transaction Performance Report Reads response Intervals of a transaction check over time. Use Resolution to pick the interval size and Include Uptime to add availability.
- Get an Alerting Contact Reads a notification contact with its Type, Owner and Notification Targets.
- Get an Alerting Team Reads a notification team and shows all of its Members.
- Get an Average Summary Averages the Responsetime and Status of a check over From to To. Use By Country or By Probe to group the result, and Include Uptime to add the uptime totals.
- Get an Hours Of Day Summary Shows the average response for each Hour of the day for a check. Turn on Use Local Time to group by the time zone of the account instead of UTC.
- Get an Outage Summary Lists the up and down periods (States) of a check from From to To. Use Order to start from the newest or the oldest.
- Get the Credits Shows the credit limits of the account, such as Checklimit, Availablechecks and Availablesms.
- Get the Reference Data Shows lookup lists of Regions, Timezones, Countries and Phonecodes.
- List Alerting Contacts Gives every notification contact with its Paused flag, Type and Notification Targets.
- List Alerting Teams Lists every notification team with their Members to see who belongs where.
- List Alerts Retrieves alerts that were sent, filtered by Check IDs, Contact IDs, Status or Sent Via, within From and To.
- List Check Results Pulls raw test results of a check, each with Probeid, Status and Responsetime. Filter by Probe IDs or response time bounds.
- List Checks Reads uptime checks with their Lasttesttime and Lastresponsetime. Use Tags to keep only checks with those tags.
- List Maintenance Occurrences Retrieves occurrences of maintenance windows from From to To, with Maintenance Window to focus on one.
- List Maintenance Windows Lists maintenance windows with their Description, Recurrencetype and Repeatevery. Use Order By to pick the sort field and Order to set the direction.
- List Probes Finds the testing locations with Country, City and Hostname. Turn on Only Active or Include Deleted to filter.
- List Probes Used By a Check Names the Probes that tested a check since From, up to To if given.
- List Root Cause Analyses Reads the root cause analyses for outages of a check between From and To, each with its Timefirsttest and Timeconfirmtest.
- List Transaction Checks Gets scripted checks with their Active flag and Interval, limited to some Tags or one Type.
- List Transaction Status Reports Shows status reports of transaction checks with their States. Turn on Omit Empty to drop checks without data.
- Make an API Call Sends a free-form request to the Pingdom REST API, signed with your saved credential.
- Run a Single Test Runs one immediate test of a Host with a Check Type, from a Probe or Probe Regions. Set Path, Port or HTTP Authentication to aim the request.
- Run a Traceroute Traces the network route to a Host, optionally from a given Probe.
- Update a Check Edits a monitor, from its Host and Check Interval (Minutes) to its Probe Regions and Contacts To Alert.
- Update a Maintenance Occurrence Moves one occurrence to a new Start and End.
- Update a Maintenance Window Edits the Description, Start, End or repeat settings of a maintenance window. Use Clear Fields to blank chosen values.
- Update a Transaction Check Edits a scripted check, covering its Steps, Region, Interval (Minutes) or Severity.
- Update an Alerting Contact Changes the Name of a notification contact, its Email Targets and SMS Targets, or sets Paused.
- Update an Alerting Team Renames a notification team or replaces its Members.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with GitHub and Pingdom integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting GitHub and Pingdom.
References
List of sources used to gather information about the GitHub and Pingdom integration.
- GitHub and Pingdom integration source code, module specs and credentials implementation.
- Our GitHub and Pingdom integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for GitHub and Pingdom, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- GitHub integration information
- Pingdom integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted GitHub and Pingdom integration page documentation. Used sources, the role of AI, and how the team validates the result.

