STEP 1
Connect Cortex and HTTP
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Cortex and HTTP Integration
Align data between Cortex and HTTP to automate developer tools workflows. Actions made in Cortex integration can trigger sequences of multiple actions inside HTTP app - automatically, without any line of code.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Cortex and HTTP
Detailed info you need to know about Cortex and HTTP integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Cortex to HTTP
Set up your Cortex and HTTP integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Cortex and HTTP 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 Cortex and HTTP. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Cortex and HTTP work in WEXTL?
WEXTL exposes actions and triggers for Cortex and HTTP that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Cortex actionsHTTP actions
Cortex modules
- Delete AnalyzerRemoves a custom analyzer registration.
- Delete JobDeletes a job record.
- Get AnalyzerReturns a single analyzer.
- Get JobReturns a single job.
- Get Job ReportReturns the report for a completed job.
- List AnalyzersRetrieves available analyzers.
- List JobsRetrieves analyzer/responder jobs.
- List RespondersRetrieves available responders.
- Make an API CallPerforms an arbitrary authorized API call.
- Run AnalyzerSubmits an observable to an analyzer.
- Run ResponderRuns a responder against a TheHive entity.
- Submit JobSubmits a file-type observable to an analyzer.
- Update Analyzer ConfigurationUpdates org-level analyzer configuration.
HTTP modules
- Download a FileDownload a file from any URL for use in later workflow steps.
- Make a GraphQL RequestSend a GraphQL query or mutation to any GraphQL endpoint and receive its data and errors.
- Send a RequestSend a request to any URL and receive the response.
Frequently asked questions
Common questions about connecting Cortex and HTTP.
Connect your Cortex and HTTP accounts once, pick an action in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: use Cortex's "Delete Analyzer" action to perform HTTP's "Download a File" action. Cortex has 13 actions (including Delete Analyzer, Delete Job, and Get Analyzer); HTTP has 3 actions (including Download a File, Make a GraphQL Request, and Send a Request). Add filters and transforms between steps when you need them. [1]
Yes — pick an action in either app, then an action in the other, and map the fields between them. [2]
No. Cortex-to-HTTP automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Cortex (or HTTP) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Cortex + HTTP automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Cortex and HTTP integration.
- Cortex and HTTP integration source code, module specs and credentials implementation.
- Our Cortex and HTTP integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Cortex and HTTP — 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.
- Cortex integration information
- HTTP integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library