Connect Postman integrations
VerifiedPostman: Manage Postman collections, environments, mock servers, monitors, specs and workspaces, connected to WEXTL workflows and AI agents. Link Postman events to the tools your engineering team already uses. Start with Watch Mock Calls, then follow with Get a Collection or Get a Collection Folder to handle the next step.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Postman integration
Triggers can detect changes in Postman and run actions that can create, search or modify data inside Postman automatically[3], exactly how you set them.
- Watch Mock Calls Polls the call log of a mock server on your schedule and fires once per call, with Response Name, Served At and Request. Use Limit to bound each poll.
- Watch Monitor Runs Looks at a monitor on your schedule and fires once per run, with Status, Started At and Finished At. Use Limit to bound each poll.
- Watch Workspace Activity Runs on your schedule and fires once for each new activity entry, with its User and Action. Use Element Type to follow one kind of item.
- 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.
- Get a Collection Update Status Polls an asynchronous collection update by Task ID and reports its Status.
- Get a Duplicate Collection Status Polls a collection copy task by Task ID and returns the Task.
- Get a Mock Response Looks up a mock server response from its Server Response ID, returning Name and Headers.
- Get a Mock Server Reads a mock server with its Name, Collection and Mock Url.
- Get a Monitor Retrieves a monitor with its Name, Owner, Active state and Notification Limit.
- Get a Pull Request Fetches a pull request through Pull Request ID, returning its Title, Description and Created By.
- Get a Source Collection Status Checks whether a forked collection has fallen behind its source and returns the Collection.
- Get a Spec Reads an API spec with its Name, Type, File Format and Created By.
- Get a Spec Definition Pulls the full definition of a spec: Openapi version, Info, Paths, Components, Servers and Security.
- Get a Spec File Reads one spec file via File Path, returning its Name, Created By and Updated By.
- Get a Spec Task Status Looks up a spec task from its Element Type, Element ID and Task ID, then reports its Status and Meta.
- Get a Team Reads a team with its Name, Handle and Description. Use Include to add more detail.
- Get a Team User Looks up a member by User ID, with Name, Username, Email and Roles.
- Get a Workspace Retrieves a workspace with its Name, Type, Visibility and Description.
- Get a Workspace Update Fetches an update post by Update ID with its Topic, Description and Created By.
- Get an API Fetches an API with its Name, Description, Created At and Git Info. Use Include to add related data.
- Get an API Schema Reads one API schema by Schema ID, including its Files. Turn on Bundled for a single merged document, or add a Version ID to read an older version.
- Get an API Schema File Opens one file inside an API schema by File Path, returning its Name, Content and Created By. Add a Version ID for an older version.
- Get an API Version Retrieves the release behind a Version ID as a Version record.
- Get an Environment Reads an environment with its Name, Owner and Values.
- Get Collection Tags Shows which Tags are attached to a collection, as a single record.
- Get Spec Version Files Reads every file stored under a tagged spec version from its Tag ID, as Data.
- Get the Current User Shows the owner of the API key stored in your credential. It returns the User details and the allowed Operations.
- Get Workspace Tags Reads the Tags attached to a workspace, one record holding all its labels.
- Get Workspace Variables Reads the global variables set on a workspace and returns them as Values.
- List API Schema Files Shows each file of an API schema with its Path, Created By and Updated At. Add a Version ID to read an older version.
- List API Versions Returns the releases of an API with their Name, Release Notes and Updated At. Set Limit to cap how many return.
- List APIs Lists the APIs in a workspace along with their Summary and Created By. Filter on Created By or Description, and cap the count with Limit.
- List Collection Comments Pulls the comments on a collection, each with a Thread Id, Status and Body. Use Limit to bound the result.
- List Collection Forks Finds the forks made from a collection, with each Fork Name and Created By. Use Direction to set the order of the list.
- List Collection Pull Requests Fetches the pull requests of a collection, with their Description, Destination Id and Href.
- List Collection Specs Gathers the specs generated from a collection, with each State and Created By.
- List Collections Lists collections across your account, returning each Name, Owner and Uid. Narrow by Workspace or Name.
- List Environment Forks Returns the forks of an environment with each Fork Name and Created By. Use Direction to set the order.
- List Environments Shows environments with their Name, Owner and Uid. Pick a Workspace to list only its environments.
- List Folder Comments Reads the comments left on a folder, with each Thread Id and Status, for the folder with the Folder ID.
- List Forked Collections Browses the collections you forked, with each Fork Name and Source Id. Use Direction to set the order.
- List Mock Calls Returns calls served by a mock server, with Response Name, Served At, Request and Response. Filter by Since, Until, Response Type, Method or Path.
- List Mock Responses Collects the server responses defined on a mock server, with Name, Created By and the reply codes.
- List Mock Servers Lists mock servers with Name, Collection and Mock Url. Narrow by Team or Workspace.
- List Monitors Shows monitors with their Name, Active state and Uid, filtered by Workspace, Owner ID, Collection or Environment.
- List Request Comments Reads comments on a request, each with a Thread Id, Status and Body, for the request with the Request ID.
- List Response Comments Retrieves comments on a saved response by Response ID, with each Created By and Updated At.
- List Spec Collections Finds the collections built from a spec, with State, Name and Created By.
- List Spec Files Pulls each file of a spec with Path, Name and Updated By.
- List Spec Version Tags Shows the tagged versions of a spec as an Id and a Name each.
- List Specs Fetches specs from a workspace with Name, Type and Created By.
- List Tagged Items Finds items that carry a Tag. Use Item Type to keep one kind, and Direction to order the list.
- List Team Users Browses the members of your team with Name, Username, Email and Roles. Add a Group ID to see one group.
- List Teams Gets your teams with Name, Handle and Description. Turn on Include Settings or Include User Roles to add those details.
- List Workspace Activity Returns the activity feed of a workspace with each User and Action. Narrow by User ID or Element Type.
- List Workspace Updates Loads the posts in a workspace with Topic and Description. Use Category to keep one kind.
- List Workspaces Lists workspaces with Name, Type, Visibility and About. Filter by Type, Created By, or an Element Type with its Element ID. Turn on Include Deactivated Mocks to add inactive mocks.
- Search Postman Searches Postman content of one Element Type. Add Search text, Ownership or Filters (JSON) to narrow the matches.
- 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.
- Make an API Call Calls the Postman REST API directly with a free-form request under your saved credential.
- Merge a Collection Fork Folds a forked Source collection into a Destination collection. Use Strategy to say what happens to the fork.
- Merge an Environment Fork Folds a forked Source environment into its parent. Turn on Delete Source to remove the fork afterwards.
- Publish a Mock Server Publishes a mock server, which Unpublish a Mock Server later reverses.
- Publish the Collection Documentation Publishes the docs of a collection with a Top Bar Color, Right Sidebar Color and Highlight Color. Add a Layout, an Environment or Customization (JSON) for more styling.
- Pull Collection Changes Brings the latest source changes into a forked collection.
- Pull Environment Changes Brings changes from a Source environment into a forked environment, keeping the fork in step with its origin.
- Remove an Environment Variable Deletes the variable with a given Key from an environment.
- Rename a Spec Retitles a spec with a new Name, returning its Type, Created By and Updated At.
- Rename an Environment Gives an existing environment the new Name.
- Replace a Collection Swaps a collection for the full Collection (JSON) supplied. Turn on Run Async to run the replacement as a background task.
- Replace an Environment Swaps the contents of an environment for a new Name and a list of Variables, each defined by Key, Value, Type and Enabled. Turn on Confirm when the new list has no variables.
- Replace Workspace Variables Rewrites the global variables in a workspace to the Variables listed. Turn on Confirm when the list is empty.
- Resolve a Comment Thread Marks the comment thread with a Thread ID as resolved, closing the discussion.
- Review a Pull Request Records a review on a pull request by Pull Request ID, using Action. A Comment can explain the decision.
- Run a Monitor Triggers a monitor immediately rather than waiting for its schedule. Turn on Run in the Background to return before the run ends.
- Set an Environment Variable Creates or edits one variable of an environment under a Key. Use Value, Type, Enabled and Description for its details.
- Set Collection Tags Assigns Tags to a collection in place of the old ones. Turn on Confirm to confirm removing all tags.
- Set Workspace Tags Assigns new Tags to a workspace in place of the existing ones. Turn on Confirm to confirm removing all tags.
- Sync a Collection with a Spec Refreshes a collection from the spec with a Spec ID, and returns a Task Id and Url for the sync.
- Sync a Spec with a Collection Refreshes a spec from a collection, reporting a Task Id and Url for the sync run.
- Transfer Collection Folders Relocates folders given as IDs to a Target ID of the Target Kind chosen. Use Mode to move or copy them, and Position with Location ID to place them.
- Transfer Collection Requests Shifts requests listed as IDs into a Target ID of the Target Kind chosen. Switch Mode between move and copy, and set Position and Location ID for placement.
- Transfer Workspace Elements Shifts the Element IDs of one Type from a workspace to a Target Workspace, and returns the Id, Type and To of the transfer.
- Unpublish a Mock Server Takes a mock server back from its published state. Publish a Mock Server reverses it.
- Unpublish the Collection Documentation Takes the published docs of a collection offline.
- Update a Collection Modifies a collection through its Name, Description, Variables, Auth (JSON) and Events (JSON), and returns the Id, Name and Description.
- Update a Collection Comment Rewrites the Comment text of a collection comment with a Comment ID. Use Tagged Users to mention people again.
- Update a Collection Folder Renames a folder or rewrites its Description, for the folder with a Folder ID.
- Update a Collection Request Revises a saved request by Request ID, with a fresh Method, URL, Headers, Query Parameters, Body Mode or Auth (JSON). Use Name to rename it.
- Update a Collection Response Adjusts a saved example reply: new Name, Status Text, Headers or Body values replace the old ones. Use Clear Fields to empty values.
- Update a Folder Comment Revises a folder comment, matched on Comment ID and Folder ID, replacing it with new Comment text.
- Update a Mock Response Alters a mock server response through a new Name, Headers, Language or Body.
- Update a Mock Server Modifies the Name, Environment, Collection, Description or Private setting of a mock. Use Version Tag to point it at a tagged version and Clear Fields to empty values.
- Update a Monitor Reschedules or renames a monitor through Name, Cron, Time Zone and Active, and tunes Retry Attempts and Notification Limit.
- Update a Request Comment Rewrites a request comment, matched on Comment ID and Request ID, using new Comment text.
- Update a Response Comment Amends a saved response comment, matched on Comment ID and Response ID, using new Comment text.
- Update a Spec File Edits one spec file by File Path, with a fresh Name, Type or Content.
- Update a Workspace Edits a workspace through a new Name, Type, Description or About. Use Clear Fields to empty values.
- Update a Workspace Update Rewrites the Topic, Description and Category of a workspace post. Turn on Pinned to pin it, and edit Related Resources to relink what it covers.
- Update an API Renames an API or rewrites its Summary and Description.
- Update an API Version Revises the Name and Release Notes of an API version by Version ID.
- Update Spec Sync Options Amends how a spec syncs with a collection. Turn on Sync Examples to sync the example responses and Delete Orphaned Requests to delete requests no longer in the specification.
How to integrate Postman in automation workflow?
Postman in three steps: start with "Watch Mock Calls", connect one credential, then add your next step.
STEP 1
Select Postman in workflow
Add the "Watch Mock Calls" trigger from Postman to the canvas[4].
STEP 2
Connect Postman
Fill in the Postman credential once. All 149 Postman modules use it[3].
STEP 3
Build a workflow
Add "Get a Collection" or "Get a Collection Folder" after it, then connect any app[5] or the HTTP node.
How Postman connects and integrates with WEXTL
Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Postman app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Postman supports.
Full Postman API documentationThe following table illustrates what fields Postman integration require during authorization flow inside our workflow builder[4].
Connect Postman
Region*Text
••••••••
API Key*Text
••••••••
| Field | Type | Help |
|---|---|---|
RegionRequired | select | Pick EU only if your team uses the EU data region. A key from the other region is rejected. |
API KeyRequired | password | In Postman open Settings, then Account settings, then API keys, and generate a key. |
Connect Postman to popular apps on WEXTL
Enter a name of the other app you want to sync with Postman below. Click on selected app to explore integration options with Postman. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.
Example automation with Postman integration
Select Watch Workspace Activity trigger from Postman - this will be a starting point in your automation. Whenever event happens in Postman, workflow will start[7] from Watch Workspace Activity node.
Search for Create a Workspace, connect it as the next step of integration sequence. You can use filters between Watch Workspace Activity and Create a Workspace, so only important data pass from Watch Workspace Activity to the next step. WEXTL gives you full control over the process of Postman automation. All parts of workflow are visible on the canvas[4].
Postman on WEXTL has 150 modules for creating developer tools automations. Explore Postman documentation for more.
- PostmanWatch Workspace Activity
- Google Cloud StoragePerforms action
OR
- Google Cloud StorageTriggers
- PostmanCreate a Workspace
Frequently asked questions
Common questions about automating Postman in your workflows.
What triggers does Postman support?
Postman has 3 triggers, including "Watch Mock Calls", "Watch Monitor Runs", and "Watch Workspace Activity". Triggers are start points of the workflow, and automations may start from them.
What actions can I run in Postman?
Integration has 147 actions, including "Get a Collection", "Get a Collection Folder", and "Get a Collection Merge Status", and more. Refer to our Postman Documentation for detailed inputs and outputs.
Do I need to write code to build automations?
No. The 149 Postman modules, like "Get a Collection", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].
Is the integration secure?
Yes. You fill in the Postman credential once. WEXTL encrypts it at rest, and only your team can use it.
How does WEXTL integrate with Postman?
Through the official Postman API: 149 modules, plus "Make an API Call" for any endpoint they don't cover[3].
Can I use webhooks with Postman?
Postman doesn't push events here, so "Watch Mock Calls", "Watch Monitor Runs", and "Watch Workspace Activity" check on the schedule you set. Anything Postman posts to a URL can start a Custom Webhook node.
Why use WEXTL platform for Postman automation?
WEXTL is an AI-first visual canvas: describe the Postman flow in plain words and AI wires the nodes[4].
References
List of sources used to gather information about the Postman integration.
- Postman integration source code, module specs and credentials implementation.
- Internal Postman integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Postman vendor API documentation, 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.
- WEXTL® Apps Library
- WEXTL® Postman App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation
How we write and maintain Postman app documentation
Explore how WEXTL® crafted Postman integration page documentation. Used sources, the role of AI, and how the team validates the result.





















