Azure Storage and Pingdom Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Connect Azure Storage 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 Azure Storage and Pingdom
Detailed info you need to know about Azure Storage and Pingdom integrations in WEXTL. Explore which modules apps support and how you connect them.
Azure Storage

Manage containers and blobs in Azure Blob Storage.[5]
Pingdom

Website and server monitoring with uptime checks, alert contacts, maintenance windows and outage reports.[6]
How to connect Azure Storage to Pingdom
Set up your Azure Storage and Pingdom integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Azure Storage 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 Azure Storage 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 Azure Storage and Pingdom. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Azure Storage and Pingdom work in WEXTL?
WEXTL exposes actions and triggers for Azure Storage 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 triggersAzure Storage 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.
Azure Storage modules
- Copy a Blob Copies a blob to a Destination container under a Destination blob name, with the copy done on the Azure side. Use Source URL to copy from another storage account, or leave it empty to copy inside this one. Returns the Copy status.
- Create a Container Adds a new container to your Azure storage account under the Container name of your choice. Use Public access to set who can read its blobs and Metadata to attach your own key and value entries. Returns the Request ID.
- Delete a Blob Removes a single blob from the container it sits in.
- Delete a Container Deletes a storage container from your Azure account. Returns the Request ID of the call.
- Get a Blob Downloads the data of one blob from a container. The blob body is returned as Content.
- Get the Metadata of a Container Retrieves the custom name and value pairs set on a container, taken from the response headers.
- Get the Properties of a Blob Shows the details Azure keeps about a blob without downloading its data, such as its Content length.
- Get the Properties of a Container Finds the details Azure reports for a container in its response headers, including the Lease status.
- List Blobs Lists the blobs inside one container, each as its own result with its Name. Use Prefix to keep only blobs whose names start with a chosen text, and Limit to set how many blobs are listed.
- List Containers Lists the containers of the storage account, each as a separate result with its Name. Use Limit to set the largest number returned.
- Make an API Call Sends a free-form request to the Azure Storage REST API, signed with your saved credential.
- Set a Blob Tier Moves a blob to another access tier. Fill Tier with the target tier. Returns the Request ID.
- Set the Metadata of a Blob Writes custom name and value pairs to a blob. Each Metadata entry takes a Header name, written in full like x-ms-meta-author, and a Value. Returns the Request ID.
- Set the Metadata of a Container Sets user-defined metadata on a container. Fill Metadata with entries made of a Header name and a Value. Returns the Request ID.
- Upload a Blob Stores new Content as a block blob under a Blob name in a container, in a single request. Set Content type to label the file. Large files may hit Azure size limits. Returns the ETag.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Azure Storage 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 Azure Storage and Pingdom.
References
List of sources used to gather information about the Azure Storage and Pingdom integration.
- Azure Storage and Pingdom integration source code, module specs and credentials implementation.
- Our Azure Storage and Pingdom integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Azure Storage 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.
- Azure Storage integration information
- Pingdom integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Azure Storage and Pingdom integration page documentation. Used sources, the role of AI, and how the team validates the result.