AWS Cognito and Pingdom Integration

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

Connect AWS Cognito 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 AWS Cognito and Pingdom

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

  • AWS Cognito

    • Developer Tools
    • 45 searches
    • 88 actions

    Amazon Cognito User Pools. Manage users, groups, app clients and identity providers with SigV4.[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 AWS Cognito to Pingdom

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

How does the integration between AWS Cognito and Pingdom work in WEXTL?

WEXTL exposes actions and triggers for AWS Cognito 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 triggersAWS Cognito 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.

AWS Cognito modules

  • Add a User Pool Client Secret Creates a secret for an app client of a user pool. Output has the Client Secret ID and the Secret Value.
  • Add Custom Attributes Extends the schema of a user pool with new custom attributes. Use Custom Attributes to supply one SchemaAttributeType object per attribute.
  • Admin Add User To Group Puts a user of the pool into a group, naming the user by Username and the group by Group Name.
  • Admin Confirm Sign Up Confirms a pending registration for a Username without the user entering a code. Use Client Metadata to pass key-value data on to your Lambda triggers.
  • Admin Create User Creates a user in a pool under a chosen Username. Leave Temporary Password empty and Cognito generates one, and use Message Action to suppress or resend the welcome message. Output includes the User Status.
  • Admin Delete Software Token Deletes the software token that a user has set up for MFA sign-in.
  • Admin Delete User Deletes a user account from a Cognito user pool, acting as an administrator on the pool.
  • Admin Delete User Attributes Removes the attributes listed under User Attribute Names from one user of a pool.
  • Admin Disable Provider For User Unlinks a federated sign-in provider from a user. Use User to give the ProviderName, ProviderAttributeName and ProviderAttributeValue of the link.
  • Admin Disable User Disables a user so the account is switched off in the pool.
  • Admin Enable User Re-enables a user whose account was switched off in the pool.
  • Admin Forget Device Makes Cognito forget a remembered device of a user, found by Device Key.
  • Admin Get Device Reads one remembered device of a user by Device Key. Output has its Created Date, plus Last Authenticated.
  • Admin Get User Looks up a user in a pool by Username. Output has their User Attributes, Enabled flag and User Status.
  • Admin Get User Auth Factors Lists the sign-in factors a user has set up, returned as Factors.
  • Admin Initiate Auth Starts a sign-in on behalf of a user with the Auth Flow of your choice. Use Auth Parameters for values such as the username and password, and Session to continue an earlier challenge. Output has a Challenge Name or an Authentication Result.
  • Admin Link Provider For User Links a federated user to an existing native user. Use Destination User for the native account and Source User for the federated one.
  • Admin List Devices Lists the remembered devices of a user. Output has the Device Key and Last Authenticated of each. Use Limit to read only part of the list.
  • Admin List Groups For User Shows the groups a user belongs to, with each Group Name, Role ARN and Precedence. Use Limit to read fewer groups.
  • Admin List User Auth Events Reads the sign-in activity recorded for a user. Each event has an Event ID, Event Type and Event Response, up to the Limit.
  • Admin Remove User From Group Removes a user from a group in a Cognito user pool, ending the membership.
  • Admin Reset User Password Forces a password reset for a user in the pool. Use Client Metadata to pass data on to your Lambda triggers.
  • Admin Respond To Auth Challenge Answers a challenge raised by Admin Initiate Auth, such as MFA, by giving the Challenge Name and Challenge Responses. Reuse the Session it returned. Output includes the Authentication Result.
  • Admin Set User MFAPreference Sets which MFA methods a user has turned on and which is preferred. Use SMS MFA Settings, Software Token MFA Settings and Email MFA Settings, each with Enabled and PreferredMfa.
  • Admin Set User Password Sets a fixed Password for a user. Turn on Permanent to keep it, otherwise it is temporary and the user must change it at the next sign-in.
  • Admin Set User Settings Sets the MFA delivery options of a user. Use MFA Options to give the delivery medium and attribute name pairs.
  • Admin Update Auth Event Feedback Marks a recorded sign-in event as Valid or Invalid with Feedback Value. Use Event ID to say which event is being rated.
  • Admin Update Device Status Marks the device with a Device Key as remembered or not remembered, using Device Remembered Status.
  • Admin Update User Attributes Changes attributes of a user with User Attributes, a list of name and value pairs. Use Client Metadata to pass data on to your Lambda triggers.
  • Admin User Global Sign Out Signs a user out everywhere by invalidating every session the user has in the pool.
  • Associate a Software Token Begins authenticator-app MFA setup for a user, using either an Access Token or the Session of a sign-in challenge. Output has the Secret Code for the app and a new Session.
  • Change Password Changes the password of the user who owns the Access Token. Use Proposed Password to set the new one.
  • Complete a Web Authn Registration Finishes passkey registration by sending the Credential response created by the authenticator, along with the Access Token of the user.
  • Confirm a Device Confirms a new device for a user by its Device Key. Use Device Name for a friendly name and Device Secret Verifier Config for the SRP verifier. Output has User Confirmation Necessary.
  • Confirm a Forgot Password Completes a forgotten-password flow by sending the Confirmation Code the user received together with a new Password for the Username. Add a Secret Hash when the app client has a secret.
  • Confirm a Sign Up Verifies a new registration with the Confirmation Code the user was sent. Use Force Alias Creation to take over an alias that already exists.
  • Create a Group Adds a group to a user pool under a Group Name. Use Role ARN to link an IAM role for members and Precedence to rank groups, where a lower number wins.
  • Create a Managed Login Branding Creates the branding of the managed login pages for an app client. Set Use Cognito Provided Values to true to inherit Cognito defaults, or supply Settings and Assets of your own. The response includes the Branding ID.
  • Create a Resource Server Registers an OAuth 2.0 resource server under an Identifier URI and a Name. Use Scopes to list the custom scopes, each with a ScopeName and ScopeDescription.
  • Create a Terms Creates a terms agreement for an app client, named with Terms Name. Use Terms Source to point to HTML in S3 or supply plain text, and set Enforcement to OPTIONAL or REQUIRED. You get the Terms ID.
  • Create a User Import Job Prepares a bulk import of users, labelled with a Job Name and logging through the CloudWatch Logs Role ARN. The Job ID and its Status are in the response.
  • Create a User Pool Creates a Cognito user pool named by Pool Name. Use Auto Verified Attributes, Username Attributes and MFA Configuration for sign-in rules, and Deletion Protection to guard the pool. The response gives the pool its ID.
  • Create a User Pool Client Adds an app client to a pool under a Client Name. Set Generate Secret to true for a client secret, and use Refresh Token Validity, Access Token Validity and ID Token Validity for token lifetimes. The response includes the Client ID.
  • Create a User Pool Domain Sets up a domain for a pool, either a prefix or a custom FQDN entered as Domain. Use Custom Domain Config to attach the certificate for a custom domain. Output includes the CloudFront Domain.
  • Create a User Pool Replica Copies a user pool into the AWS region given as Region Name. The replica comes with its own ID, Name and Status.
  • Create an Identity Provider Adds a federated provider to a pool from a Provider Name, a Provider Type such as SAML, Google or OIDC, and its Provider Details. Use Attribute Mapping to map provider attributes onto pool attributes.
  • Delete a Group Deletes a group from a Cognito user pool.
  • Delete a Managed Login Branding Deletes a managed login branding configuration from a user pool.
  • Delete a Resource Server Removes an OAuth resource server from a user pool.
  • Delete a Terms Deletes a terms agreement from a Cognito user pool.

Explore alternative integrations

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

Automate AWS Cognito and Pingdom on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS Cognito and Pingdom.

How do I connect AWS Cognito and Pingdom?

Connect your AWS Cognito 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 AWS Cognito and Pingdom?

Example: when the "Watch Alerts" trigger in Pingdom fires, WEXTL can "Add a User Pool Client Secret" in AWS Cognito. AWS Cognito has 133 actions (including Add a User Pool Client Secret, Add Custom Attributes, and Admin Add User To Group). 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 AWS Cognito trigger actions in Pingdom, and Pingdom in AWS Cognito?

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 AWS Cognito and Pingdom?

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

Does AWS Cognito integrate with Pingdom in real time?

Yes. Trigger-based automations start the moment AWS Cognito (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 AWS Cognito + 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 AWS Cognito with Pingdom?

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

References

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

  1. AWS Cognito and Pingdom integration source code, module specs and credentials implementation.
  2. Our AWS Cognito and Pingdom integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for AWS Cognito 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. AWS Cognito 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 AWS Cognito and Pingdom integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore AWS Cognito and Pingdom, or get started