AWS Cognito and Postman Integration

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

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

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

  • Postman

    • Developer Tools
    • 3 triggers
    • 59 searches
    • 88 actions

    Manage Postman collections, environments, mock servers, monitors, specs and workspaces.[6]

How to connect AWS Cognito to Postman

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

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

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

Postman triggersAWS Cognito actions

Postman modules

  • Add a Collection to an API Attaches collection content to an API from an Operation Type and Data (JSON). It returns the stored Data and Operation Type.
  • Create a Collection Starts a collection in a workspace. Prefill it with Items (JSON), Variables, Auth (JSON) and Events (JSON), or add a Description. It returns the Id, Name and Uid.
  • Create a Collection Comment Leaves a Comment on a whole collection. Use Thread ID to reply in an existing thread, and Tagged Users to mention people by User ID or Username.
  • Create a Collection Folder Makes a folder in a collection from a Name. Use Parent Folder ID to nest it inside another folder.
  • Create a Collection Pull Request Opens a pull request that proposes merging a forked collection into a Destination. Assign Reviewers, give it a Title and add a Description to explain the change.
  • Create a Collection Request Saves an API request in a collection with its Method, URL, Headers, Query Parameters and body. Use Folder ID to file it in a folder, or add Auth (JSON) and Events (JSON).
  • Create a Collection Response Stores an example reply under the request with the Request ID. Add Status Text, Headers and a Body, and use Body Language for the syntax of the Body.
  • Create a Collection Webhook Sets up a webhook for a collection under a Name. Add an Environment to run the collection with.
  • Create a Folder Comment Posts a Comment on one folder of a collection, using the Folder ID. Use Thread ID to answer an existing thread and Tagged Users to mention people.
  • Create a Mock Response Defines a server response on a mock server from a Name. Use Headers, Language and Body to shape what the mock sends back.
  • Create a Mock Server Spins up a mock server from a collection in a workspace. Pick an Environment, give it a Name, and set Private to restrict callers. It returns the Mock Url.
  • Create a Monitor Schedules a collection run on a Cron expression in a Time Zone. Turn on Active to run it, and tune Retry Attempts, Notification Limit, Email on Error and Email on Failure.
  • Create a Request Comment Writes a Comment on one request of a collection, using its Request ID. Reply in a thread with Thread ID or mention people through Tagged Users.
  • Create a Response Comment Adds a Comment to a saved example, using its Response ID. Set Thread ID to continue a thread, or Tagged Users to mention teammates.
  • Create a Spec Writes an API spec into a workspace from a Name, a Type and its Files. Each file carries a Path and its Content.
  • Create a Spec File Puts another file into a spec at the Path of your choice, along with its Content. The new file returns with its Id, Created At and Created By.
  • Create a Spec Version Tag Marks the current state of a spec with a Name, giving you a version to return to later.
  • Create a Workspace Opens a workspace from a Name and a Type. Add context with Description and About, and assign it to a team through Team.
  • Create a Workspace Update Publishes a post to a workspace with a Topic, a Description and a Category. Add Related Resources, each with a Resource and Resource ID, to link what it covers.
  • Create an API Registers an API in a workspace from a Name, with an optional Summary and Description. The API is returned with those three values.
  • Create an API Version Releases a version of an API from a Name. Link Schema IDs and Collection IDs to it, and add Release Notes to explain what changed.
  • Create an Environment Builds an environment in a workspace from a Name. Add Variables, each with a Key, Value, Type, Enabled flag and Description, to start with values.
  • Delete a Collection Deletes a collection, the saved set of folders and requests.
  • Delete a Collection Comment Deletes the collection comment that carries a Comment ID.
  • Delete a Collection Folder Removes the folder with a given Folder ID from its collection.
  • Delete a Collection Request Deletes a single request from its collection, using Request ID.
  • Delete a Collection Response Removes a saved example response from its request, using Response ID.
  • Delete a Folder Comment Removes a folder comment by its Comment ID, from the Folder ID folder.
  • Delete a Mock Response Removes a mock server response by Server Response ID.
  • Delete a Mock Server Removes a mock server, the fake API backed by a collection.
  • Delete a Monitor Removes a scheduled monitor from your Postman account.
  • Delete a Request Comment Removes a request comment by Comment ID, under the request with the Request ID.
  • Delete a Response Comment Removes a comment by Comment ID from the saved response with the Response ID.
  • Delete a Spec Deletes an API spec from your workspace.
  • Delete a Spec File Deletes one file from an API spec by File Path.
  • Delete a Workspace Deletes a workspace once Confirm is turned on.
  • Delete a Workspace Update Removes an update post by its Update ID from a workspace.
  • Delete an API Deletes an API definition from Postman.
  • Delete an API Version Deletes the release that matches a Version ID from the version list of an API.
  • Delete an Environment Deletes a named environment, the variable set of a workspace.
  • Duplicate a Collection Copies a collection into a target Workspace. Use Suffix to tell the copy apart from the original.
  • Fork a Collection Forks a collection into a target Workspace. Use Label to name the fork.
  • Fork an Environment Makes a fork of an environment in a Workspace. Use Fork Name to title the fork.
  • Generate a Collection from a Spec Builds a collection out of an API spec under a Name. Use Folder Strategy, Indent Character and Include Deprecated to shape it. It returns a Task Id and Url for following the run.
  • Generate a Spec from a Collection Writes an API spec out of a collection from a Name, using Type and Format to set the spec style. Follow the run with its Task Id and Url.
  • Get a Collection Downloads a whole collection: Info, Item, Auth, Event and Variable. Use Model to switch the response format and Access Key to read a shared collection.
  • Get a Collection Folder Pulls one folder by Folder ID, returning its Name, Description and Owner. Turn on Populate to include what is inside.
  • Get a Collection Merge Status Polls a merge task by Task ID and reports its Status.
  • Get a Collection Request Looks up one request by Request ID, returning its Name, Owner and Last Revision. Turn on Populate for more detail.
  • Get a Collection Response Fetches the saved example response behind a Response ID, with the Request it belongs to, plus its Name and Owner.

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

Automate AWS Cognito and Postman on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS Cognito and Postman.

How do I connect AWS Cognito and Postman?

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

Example: when the "Watch Mock Calls" trigger in Postman 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). Postman has 147 actions (including Add a Collection to an API, Create a Collection, and Create a Collection Comment). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore AWS Cognito and Postman, or get started