AWS Cognito and Rootly Integration

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

Keep AWS Cognito and Rootly matched by integrating their events and actions. When developer tools events happen in AWS Cognito, update the Rootly 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 Cognito and Rootly

Detailed info you need to know about AWS Cognito and Rootly 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]

  • Rootly

    • Developer Tools
    • 1 trigger
    • 63 searches
    • 86 actions

    Incident management and on-call platform for detecting, responding to, and learning from incidents.[6]

How to connect AWS Cognito to Rootly

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

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

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

Rootly triggersAWS Cognito actions

Rootly modules

  • Watch Events (Instant) Starts a workflow as soon as Rootly sends a webhook event, the moment it happens.
  • Acknowledge an Alert Marks an alert as acknowledged. Use Actor Email to record a specific user as the one who did it, when your organization has actor attribution turned on.
  • Add a Note to an Alert Writes a Note on the activity feed of an alert, credited to the chosen User.
  • Add a Timeline Event to an Incident Writes an Event on the timeline of an incident. Set Visibility to control who can read it.
  • Add Subscribers to an Incident Subscribes the chosen Users to updates on an incident. Turn on Skip Users Without Access to a Private Incident to leave out anyone who cannot see it.
  • Assign a Role to a User on an Incident Gives a user an Incident Role on a single incident and returns the updated incident.
  • Attach Alerts to an Incident Links existing alerts to an incident by their Alert IDs and returns the Incident ID with its Alerts.
  • Cancel an Incident Cancels an incident, with an optional Cancellation Message giving the reason.
  • Create a Cause Adds a cause that incidents and retrospectives can be traced to. Give it a Name, and a Public Name and Public Description for status pages.
  • Create a Functionality Adds a functionality, a capability of your product, from its Name. Link Owner Teams, Owner Users, Environments and Services to show who is behind it.
  • Create a Heartbeat Sets up a heartbeat that alerts when pings stop. Define the Interval with its Interval Unit, an Alert Summary, and who to page through Notification Target Type and Notification Target ID.
  • Create a Pulse Records a pulse from its Summary. Link Services and Environments, and use Labels, References and Data for extra detail.
  • Create a Schedule Creates an on-call schedule from a Name and an Owner. Use Time Zone, Owner Teams and Send Shift Reports to adjust it.
  • Create a Service Registers a service from its Name. Link Owner Teams, Owner Users, Related Services and an Alert Urgency to place it in the rest of your setup.
  • Create a Severity Adds a severity level from a Name. Use Severity Level to rank how serious it is, and Color and Notify Emails to customise it.
  • Create a Status Page Builds a status page titled by Title. Turn Public and Enabled on or off, style it with Header Color and Footer Color, and choose Services and Functionalities to cover.
  • Create a Status Page Announcement Posts an announcement to a status page, from its Title and Body. Turn on Notify Subscribers to alert followers.
  • Create a Sub-Status Adds a sub-status under a Parent Status, from a Name. Use Position to order it among its siblings.
  • Create a Team Forms a responder team called Name. Add Members and Admins, a Color and an Alert Urgency, and switch on Alerts by Email.
  • Create an Action Item Adds a follow-up task to an incident from its Summary. Set a Kind, Priority and Due Date, and name an Assignee or Assigned Teams to own it.
  • Create an Alert Raises an alert from a Summary. Link Services, Teams and Environments, choose an Alert Urgency, and page someone with Notification Target Type and Notification Target ID.
  • Create an Alert Urgency Defines an urgency level from a Name and Description. Use Retrigger After to set how long Rootly waits before alerting again on an unacknowledged alert.
  • Create an Environment Adds an environment such as production, from its Name. Use Notify Emails, Color and External ID to describe and link it.
  • Create an Escalation Policy Builds an escalation policy from a Name. Use Repeat Count to loop it several times, and Teams and Services to attach it.
  • Create an Incident Declares an incident. Add a Title, Severity and Summary, link Services, Environments and Incident Types, and set Private to restrict who can see it.
  • Create an Incident Role Defines a role people can hold during incidents, from a Name. Turn on Optional, Enabled or Allow Several Users to shape it.
  • Create an Incident Type Adds a type for classifying incidents, from a Name. Use Color and Notify Emails to customise it.
  • Create an Override Shift Puts a User on call for a window on a schedule, between Starts At and Ends At in UTC.
  • Delete a Cause Deletes a cause used to classify incidents.
  • Delete a Functionality Removes a functionality, a product capability, from the catalog.
  • Delete a Heartbeat Deletes a heartbeat monitor that expected regular pings.
  • Delete a Schedule Removes an on-call schedule from Rootly.
  • Delete a Service Deletes the chosen service from the Rootly account.
  • Delete a Severity Removes a severity level used for incidents.
  • Delete a Status Page Deletes a customer-facing status page from Rootly.
  • Delete a Status Page Announcement Removes an announcement posted on a status page.
  • Delete a Status Page Event Deletes an incident update that was posted to a status page.
  • Delete a Sub-Status Deletes a sub-status that sits under a parent status.
  • Delete a Team Removes a team from Rootly once Confirm is turned on, because it cannot be undone.
  • Delete an Action Item Deletes an action item from Rootly. Turn on Confirm to go ahead, because it cannot be undone.
  • Delete an Alert Urgency Removes an urgency level that alerts can carry.
  • Delete an Environment Removes an environment from your Rootly catalog.
  • Delete an Escalation Policy Deletes a paging policy from Rootly.
  • Delete an Incident Removes an incident and its record from Rootly.
  • Delete an Incident Role Removes a role that responders can take during incidents.
  • Delete an Incident Timeline Event Deletes one chronology entry from the timeline of an incident.
  • Delete an Incident Type Removes a type used to classify incidents.
  • Delete an Override Shift Deletes a temporary on-call override from a schedule.
  • Detach an Incident from Its Parent Separates a child incident from the parent incident it was grouped under.
  • Escalate an Alert Raises an alert to a higher level of an escalation policy. Name the Escalation Policy and Escalation Policy Level, or leave the level empty for the next one.

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 Rootly integrations. Pick any from the list below if the current combination isn't the one you need.

Automate AWS Cognito and Rootly on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS Cognito and Rootly.

How do I connect AWS Cognito and Rootly?

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

Example: when the "Watch Events (Instant)" trigger in Rootly 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). Rootly has 149 actions (including Acknowledge an Alert, Add a Note to an Alert, and Add a Timeline Event to an Incident). Add filters and transforms between steps when you need them.[1]

Can AWS Cognito trigger actions in Rootly, and Rootly 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 Rootly?

No. AWS Cognito-to-Rootly 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 Rootly in real time?

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

You can build your AWS Cognito + Rootly 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 Rootly integration.

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

Explore AWS Cognito and Rootly, or get started