AWS Lambda and Pingdom Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Keep AWS Lambda and Pingdom matched by integrating their events and actions. When developer tools events happen in AWS Lambda, update the Pingdom automatically - without any line of code in visual workflow builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about AWS Lambda and Pingdom
Detailed info you need to know about AWS Lambda and Pingdom integrations in WEXTL. Explore which modules apps support and how you connect them.
AWS Lambda

Serverless compute that runs your code without managing servers.[5]
Pingdom

Website and server monitoring with uptime checks, alert contacts, maintenance windows and outage reports.[6]
How to connect AWS Lambda to Pingdom
Set up your AWS Lambda and Pingdom integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect AWS Lambda 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 AWS Lambda 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 AWS Lambda and Pingdom. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between AWS Lambda and Pingdom work in WEXTL?
WEXTL exposes actions and triggers for AWS Lambda 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.
AWS Lambda triggersPingdom actions
AWS Lambda modules
- Watch Durable Executions Polls a function and fires once for every durable execution that began since the previous check. Use Status to watch only one state, and Limit for how many the first check emits.
- Add a Function Permission Lets another service, account or role use a function by adding a statement to its resource policy. Use Action and Principal to say who may do what, and Source ARN to limit it to one calling resource.
- Add a Layer Version Permission Shares a layer version with an account by adding a policy statement. Use Principal * with Organization ID to open it to one organization, and Revision ID to skip the change if the policy moved on since you read it.
- Add Tags to a Resource Attaches Tags to the resource behind the Resource ARN. A tag whose key already exists gets the new value.
- Cancel a Durable Execution Stops a durable execution. Use Error Message to record why it was stopped, and Error Type, Error Data or Stack Trace to attach error details. Output is the Stop Timestamp.
- Create a Capacity Provider Sets up a capacity provider that runs functions on compute instances in your own subnets. It needs VPC Config and Permissions Config. Use Scaling Config to set how it scales and Instance Requirements to limit the instance types.
- Create a Code Signing Config Defines which signing profiles may sign code for functions, through Allowed Publishers. Use Code Signing Policies to decide what happens when a signature check fails.
- Create a Durable Execution Checkpoint Saves progress of a durable execution against its current Checkpoint Token. Use Updates for state changes such as completing a step or starting a wait. Output includes the next Checkpoint Token.
- Create a Function Deploys a new Lambda function under a Role, from your Code. For zip packages add a Runtime and Handler, and for container images an image URI. Use Timeout and Memory Size to replace the defaults of 3 seconds and 128 MB.
- Create a Function URL Config Gives a function a dedicated HTTPS endpoint. Use Auth Type to choose between AWS IAM and open access, Invoke Mode for buffered or streamed answers, and Cors for cross-origin rules.
- Create an Alias Adds a named alias that points to a version of a function. Use Routing Config to send a share of the traffic to a second version.
- Create an Event Source Mapping Connects a function to a stream, queue or broker and has records delivered in batches. Use Event Source ARN for a Kinesis or DynamoDB stream, an SQS queue or another source, and Batch Size to bound each batch.
- Delete a Capacity Provider Removes a capacity provider from the account and returns its final Capacity Provider record.
- Delete a Code Signing Config Deletes a code signing config from your Lambda account.
- Delete a Function Deletes a function. Use Qualifier to delete a single version, otherwise the function goes with all of its versions and aliases.
- Delete a Function Code Signing Config Unlinks a function from the code signing config that it was bound to.
- Delete a Function Concurrency Clears the reserved concurrency set on a function.
- Delete a Function Event Invoke Config Removes the retry and destination settings for asynchronous calls. Use Qualifier to target a version or alias, or leave it empty for the latest version.
- Delete a Function URL Config Removes the HTTPS endpoint of a function, or of one alias when Qualifier names it.
- Delete a Layer Version Deletes a numbered version of a layer from Lambda.
- Delete a Provisioned Concurrency Config Removes the warm capacity set on one version or alias, chosen with Qualifier.
- Delete a Resource Policy Removes the policy that sits on a function or layer version. Use Revision ID to delete only if the current revision matches, or leave it empty to delete regardless.
- Delete an Alias Deletes one alias of a function by its name.
- Delete an Event Source Mapping Removes the link between a function and its stream, queue or broker. The final mapping settings are returned.
- Get a Capacity Provider Looks up a capacity provider and returns its full Capacity Provider record.
- Get a Code Signing Config Retrieves a code signing config, including its allowed publishers and policy, as Code Signing Config.
- Get a Durable Execution Shows the status of one durable execution with its start and end timestamps. Turn off Include Execution Data to leave out the input, result and error and get a smaller response.
- Get a Durable Execution History Lists the events recorded for a durable execution, such as when it started, succeeded or failed. Use Newest First to reverse the order, and Include Execution Data to turn step results and callback payloads on or off.
- Get a Durable Execution State Returns the operations of a durable execution as of a given Checkpoint Token, with the Status and details of each step, wait or callback. Use Limit to bound a run.
- Get a Function Returns a function in full, with its Configuration, Code details and Tags. Add a Qualifier to read one version or alias, and expect environment variable values in the output.
- Get a Function Code Signing Config Checks which code signing config is attached to a function and returns its Code Signing Config ARN.
- Get a Function Concurrency Looks up how many concurrent executions are reserved for a function, as Reserved Concurrent Executions.
- Get a Function Configuration Pulls the settings of a function, such as its Runtime, Handler, Timeout and Memory Size, without the code details. Add a Qualifier to pick a version or alias, and environment variable values are included.
- Get a Function Event Invoke Config Reads how a function handles asynchronous calls: Maximum Retry Attempts, Maximum Event Age In Seconds and the Destination Config.
- Get a Function Policy Returns the resource-based policy of a function as Policy, along with its Revision ID for later guarded changes.
- Get a Function Recursion Config Shows what Lambda does with a function that calls itself in a loop, as the Recursive Loop setting.
- Get a Function Scaling Config Returns the Applied Function Scaling Config and the Requested Function Scaling Config of a given version or alias.
- Get a Function URL Config Reads the function URL configuration of a function. Output includes the Function URL, Auth Type, Invoke Mode and Cors.
- Get a Layer Version Retrieves one version of a layer, its Description, Compatible Runtimes and License Info, plus a Content location.
- Get a Layer Version by ARN Looks up a layer version from its full Layer Version ARN, including its Description, Compatible Runtimes and License Info.
- Get a Layer Version Policy Returns the permissions granted on a layer version as Policy, together with its Revision ID.
- Get a Provisioned Concurrency Config Checks warm capacity of a function alias or version. It compares Requested Provisioned Concurrent Executions with Available Provisioned Concurrent Executions and gives the Status.
- Get a Resource Policy Reads the access policy of a Lambda function or layer version, found from its Resource ARN. Output includes the Policy and Revision ID.
- Get a Runtime Management Config Shows how a function picks up runtime updates through Update Runtime On, along with its Runtime Version ARN.
- Get Account Settings Reads the Lambda limits for your account together with how much of them is in use, as Account Limit and Account Usage.
- Get an Alias Fetches an alias of a function, giving the version it points to, its Routing Config and its Revision ID.
- Get an Event Source Mapping Reads the settings of a mapping between a function and an event source, such as its Batch Size and Starting Position.
- Invoke a Function Runs a Lambda function with a JSON Payload as its input, up to 6 MB. Use Invocation Type to wait for the result or return at once, and Qualifier to run a version or alias. Turn off Stop On Function Error to branch on failures.
- List Aliases Shows the aliases of one function, each with its Name, Function Version and Routing Config. Use Function Version to keep only aliases that point to one version.
- List Capacity Providers Lists the capacity providers of your account along with their State and VPC Config. Use State to keep only providers in one state.
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 AWS Lambda 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 AWS Lambda and Pingdom.
References
List of sources used to gather information about the AWS Lambda and Pingdom integration.
- AWS Lambda and Pingdom integration source code, module specs and credentials implementation.
- Our AWS Lambda and Pingdom integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for AWS Lambda 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.
- AWS Lambda integration information
- Pingdom integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted AWS Lambda and Pingdom integration page documentation. Used sources, the role of AI, and how the team validates the result.