Adafruit and Pingdom Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect Adafruit 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 Adafruit and Pingdom

Detailed info you need to know about Adafruit and Pingdom integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Adafruit

    • Developer Tools
    • 2 searches
    • 8 actions

    Adafruit IO cloud for IoT feeds, groups, and device data streams.[5]

  • Pingdom

    • Developer Tools
    • 2 triggers
    • 29 searches
    • 22 actions

    Website and server monitoring with uptime checks, alert contacts, maintenance windows and outage reports.[6]

How to connect Adafruit to Pingdom

Set up your Adafruit and Pingdom integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Adafruit and Pingdom work in WEXTL?

WEXTL exposes actions and triggers for Adafruit 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.

Pingdom triggersAdafruit actions

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.

Adafruit modules

  • Add a Feed to a Group Puts an existing Adafruit IO feed into a group, given a Feed Key and a Group Key. Output includes the feed Name, Key and Groups.
  • Create a Data Record Stores a new data point in a feed with the Value you send. Add Latitude, Longitude and Elevation to record where it was taken. Output includes the new record ID and its Created at time.
  • Create a Feed Adds a new feed to your Adafruit IO account under a Name. Set Group Key to place it in a group right away. Output includes the new Key and ID.
  • Create a Feed in a Group Makes a new feed directly inside the group named by Group Key. Give it a Name and the feed arrives with its Key and Groups. Use Add a Feed to a Group for a feed that already exists.
  • Delete a Feed Deletes one feed from your Adafruit IO account, found by its Feed Key.
  • Get a Feed Looks up one feed by its Feed Key and returns its Name, Description, Unit Type, Unit Symbol and Last Value.
  • List Feed Data Reads the data points stored in one feed. Use Start Time and End Time to keep to a time range, and Limit to set how many records are returned. Each record has its Value, Created at time and Location.
  • Make an API Call Makes an authorized free-form request to the Adafruit REST API with your saved credential.
  • Remove a Feed from a Group Unlinks a feed from a group, given the Group Key and the Feed Key. Output lists the Groups the feed belongs to.
  • Update a Feed Changes the Name or the Group Key of the feed identified by Feed Key. Use JSON to send other feed properties as raw data. Returns the updated feed.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Adafruit and Pingdom integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Adafruit and Pingdom on WEXTL®

Claim your 3-day trial to build Adafruit with Pingdom integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Adafruit and Pingdom.

How do I connect Adafruit and Pingdom?

Connect your Adafruit and Pingdom accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Adafruit and Pingdom?

Example: when the "Watch Alerts" trigger in Pingdom fires, WEXTL can "Add a Feed to a Group" in Adafruit. Adafruit has 10 actions (including Add a Feed to a Group, Create a Data Record, and Create a Feed). Pingdom has 51 actions (including Create a Check, Create a Maintenance Window, and Create a Transaction Check). Add filters and transforms between steps when you need them.[1]

Can Adafruit trigger actions in Pingdom, and Pingdom in Adafruit?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Adafruit and Pingdom?

No. Adafruit-to-Pingdom automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Adafruit integrate with Pingdom in real time?

Yes. Trigger-based automations start the moment Adafruit (or Pingdom) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Adafruit + Pingdom integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Adafruit with Pingdom?

You can build your Adafruit + Pingdom automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Adafruit and Pingdom integration.

  1. Adafruit and Pingdom integration source code, module specs and credentials implementation.
  2. Our Adafruit and Pingdom integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Adafruit and Pingdom, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Adafruit integration information
  6. Pingdom integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Adafruit and Pingdom integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Adafruit and Pingdom, or get started