Agenty and Postman Integration
Build developer tools workflows between Agenty and Postman on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Agenty and Postman
Detailed info you need to know about Agenty and Postman integrations in WEXTL. Explore which modules apps support and how you connect them.
Agenty

Cloud web scraping, crawling and change detection. Create and run scraping, crawling and monitoring agents, feed them URLs or stored lists, start jobs on demand or on a schedule, pull the extracted rows and logs, and react when a job completes.[5]
Postman

Manage Postman collections, environments, mock servers, monitors, specs and workspaces.[6]
How to connect Agenty to Postman
Set up your Agenty and Postman integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Agenty and Postman
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 Agenty and Postman 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 Agenty and Postman. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Agenty and Postman work in WEXTL?
WEXTL exposes actions and triggers for Agenty 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.
Agenty triggersPostman actions
Agenty modules
- Watch Agent Jobs Starts the workflow instantly through a webhook, as soon as an agent job finishes or fails.
- Add Agents to a Project Files existing agents under an Agenty project. Use Agents to list which ones to include.
- Add Rows to a List Adds rows to a stored list. Use Rows for free-form row objects, which are sent as the entire request body.
- Cancel a Running Job Stops a job that is still running in Agenty. Use Agent to narrow the job choices to one agent.
- Change Agent Schedule Status Switches the run schedule of an agent on or off. Turn on Enabled to activate the schedule, or turn it off to pause it.
- Change API Key Status Changes the status of an Agenty API key by its numeric id from the API keys page. How the new status is chosen is undocumented and may toggle, so a retry may not be safe.
- Change Workflow Status Enables or disables an Agenty automation, which this app calls a workflow. Turn on Enabled to activate it, or turn it off to stop it from firing. Output returns Enabled.
- Copy an Agent Makes a duplicate of an existing agent. Add a Name to title the copy, bearing in mind the copy body is undocumented and the name goes out only if present.
- Create a List Creates a stored list. Give it a Name of up to 100 characters, and add a Description of up to 250 if useful. Output has the List ID.
- Create a Project Opens a new project for organizing agents. Add a Name to title it and a Description to explain it.
- Create a Workflow Sets up an Agenty automation, called a workflow here. It watches Agents for events chosen with Fire On, such as Job Failed or Change Detected, then runs its Actions. Use Enabled to start it on or off.
- Create an Agent Builds a new agent from a Name, a Type such as Scraping or Crawling, an Input to run against and a Config whose shape depends on the Type. Turn on Start after creation to run it straight away. Output gives the Agent ID.
- Create an API Key Generates a new API key in your Agenty account. Use Name as its display name, although the create body is undocumented and the name goes through only if present.
- Delete a Connection Removes a stored OAuth grant, and automations whose actions reference it will fail.
- Delete a List Deletes a stored list from Agenty. Removal is one-way.
- Delete a List Row Removes one row from a stored list, using the Row ID. The id is a string, even though list ids are numbers. The deletion sticks.
- Delete a Workflow Deletes an Agenty automation, which this app calls a workflow. Deleted items are lost.
- Delete Agents by Id Deletes several agents in a single call. Deleted data is lost.
- Delete an Agent Deletes one agent from your Agenty account. It stays removed.
- Delete an Agent Schedule Removes the run schedule that was set on an agent.
- Delete an API Key Deletes an Agenty API key. Nothing guards against deleting the very key this credential authenticates with. Deletion is one-way.
- Delete Projects by Id Deletes several projects in one call. It stays gone.
- Delete Rows by Id Removes several rows from a stored list at once. Fill Row IDs with their ids as one comma-separated string.
- Delete Users by Id Removes team members from your Agenty account. Deleted items stay gone.
- Download a Job Result Downloads the result of one job as a file. Use Collection to pick which output collection by number, Format for the file type, and Search to narrow the rows.
- Download API Keys as CSV Saves your API keys as a CSV file, narrowed with a Search text and arranged by Sort.
- Download Jobs as CSV Pulls job records into a CSV file, for every agent or for just one Agent. Order them with Sort.
- Download List Rows as CSV Writes every row of one stored list to a single CSV file.
- Get a Job Reads one agent job. Use Agent to narrow the job choices, then name the Job to read.
- Get a Job Output File Fetches one file produced by a job. Use File Name exactly as it appears in the job result.
- Get a Job Result Reads the rows a job produced. Use Collection to read a later collection than the first, Format for the result format, and Sort, Order or Search to shape the rows.
- Get a List Fetches a stored list record, giving its List ID, Name and Description.
- Get a List Row Fetches one row from a stored list. Give Row ID as a string here, since the row schema documents no stable id field.
- Get a Project Fetches the record of one Agenty project, to read its details.
- Get a User Looks up one team member, giving the User ID, Name, Email and Role.
- Get a Workflow Reads one automation with its Workflow ID, Name and the Agents it watches.
- Get an Account Usage Report Reads the usage dashboard of your Agenty account for a time window, running from Start to End, both inclusive.
- Get an Agent Fetches one agent, including its Agent ID, Project ID and Name.
- Get an Agent Input Shows what an agent is set to run against, as a Type and its Data.
- Get an Agent Schedule Reads the schedule attached to an agent, giving the next and the last run times as Next Scheduled Run At and Last Scheduled Run At.
- Get an API Key Looks up one API key by the numeric id shown on the API keys page in Agenty. There is no picker, because listing keys can expose secret material.
- Get Lists Browses your stored lists. Fill Search with free text to narrow them, and add Order to set the direction.
- Get the Latest Agent Result Reads the most recent result of an agent. Agenty requires Download on this read, to choose between inline rows and a file. Add Collection, Sort, Order or Search to narrow what is read.
- Invite a User Invites someone to join your Agenty team by Email. Use Role to grant owner, admin or manager access, and Name to add a display name.
- List Agents Shows the agents in your account, filtered by a Search text and ordered with Sort and Order.
- List API Keys Retrieves your Agenty API keys, optionally narrowed by a Search text.
- List Connections Lists the OAuth connections stored in your Agenty account.
- List Job Logs Reads the log lines of one job, narrowed by Search or arranged by Sort.
- List Jobs Finds agent jobs across every agent, or only those of one Agent. Add Order to choose the direction.
- List Projects Gives you the projects that group your agents, with an optional Search filter.
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.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Agenty and Postman integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Agenty and Postman.
References
List of sources used to gather information about the Agenty and Postman integration.
- Agenty and Postman integration source code, module specs and credentials implementation.
- Our Agenty and Postman integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Agenty and Postman, 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.
- Agenty integration information
- Postman integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Agenty and Postman integration page documentation. Used sources, the role of AI, and how the team validates the result.