Cortex and Postman Integration

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

Connect Cortex and Postman 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 Cortex and Postman

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

  • Cortex

    • Developer Tools
    • 6 searches
    • 7 actions

    Run TheHive Cortex analyzers and responders, and track their jobs.[5]

  • Postman

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

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

How to connect Cortex to Postman

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

How does the integration between Cortex and Postman work in WEXTL?

WEXTL exposes actions and triggers for Cortex 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 triggersCortex 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.

Cortex modules

  • Delete a Job Deletes the record of an analyzer or responder job from Cortex, using the Job ID of the run to remove.
  • Delete an Analyzer Deletes an analyzer from Cortex and returns its ID.
  • Get a Job Fetches a Cortex job by Job ID. Check its Status to see whether the analysis has finished.
  • Get a Job Report Downloads the report of a finished job for a Job ID. Output is the Full report exactly as Cortex produced it.
  • Get an Analyzer Looks up a single analyzer by Analyzer ID. You receive its ID and Name.
  • List Analyzers Shows the analyzers set up in Cortex, each with an ID and Name. Use Limit to cap how many analyzers are returned.
  • List Jobs Searches Cortex jobs and returns an ID and Status for each. Filter by Data type filter, Data filter or Analyzer filter, and set Limit for the maximum.
  • List Responders Gives every responder registered in Cortex along with its ID and Name. Set Limit to stop after a fixed number.
  • Make an API Call Makes an authorized free-form request to the Cortex REST API with your saved credential.
  • Run a Responder Starts a responder on a TheHive Case, Task, Observable, Alert or Log, named by Object type and Object ID. Add Responder parameters for extra settings. Output returns the Job ID.
  • Run an Analyzer Sends Observable data of a given Data type to an analyzer and starts a new job, returning its Job ID and Status. Set TLP, write a Message, or pass Analyzer parameters for options the analyzer defines itself.
  • Submit a Job Uploads a File for analysis and returns the new Job ID. A TLP level and a Message can travel with the submission.
  • Update an Analyzer Configuration Changes the Configuration of an analyzer, along with its Rate limit and Rate unit. Output returns the ID of the analyzer.

Explore alternative integrations

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

Automate Cortex and Postman on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Cortex and Postman.

How do I connect Cortex and Postman?

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

Example: when the "Watch Mock Calls" trigger in Postman fires, WEXTL can "Delete a Job" in Cortex. Cortex has 13 actions (including Delete a Job, Delete an Analyzer, and Get a Job). 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 Cortex trigger actions in Postman, and Postman in Cortex?

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 Cortex and Postman?

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

Does Cortex integrate with Postman in real time?

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

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

References

List of sources used to gather information about the Cortex and Postman integration.

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

Explore Cortex and Postman, or get started