STEP 1
Connect Cortex and Splunk
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 Splunk Integration
Keep Cortex and Splunk in sync by integrating their events and actions. When developer tools events happen in Cortex, update the Splunk automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Cortex and Splunk
Detailed info you need to know about Cortex and Splunk integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Cortex to Splunk
Set up your Cortex and Splunk integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Cortex and Splunk 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 Splunk. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Cortex and Splunk work in WEXTL?
WEXTL exposes actions and triggers for Cortex and Splunk 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.
Splunk triggersCortex actions
Splunk modules
- Acknowledge Saved SearchAcknowledges the saved Search.
- Control Search JobControls the search Job.
- Create Automatic LookupCreates the automatic Lookup.
- Create Calculated FieldCreates the calculated Field.
- Create Data ModelCreates the data Model.
- Create Event TypeCreates the event Type.
- Create Field AliasCreates the field Alias.
- Create Field ExtractionCreates the field Extraction.
- Create HTTP InputCreates the hTTP Input.
- Create IndexCreates the index.
- Create KV Store CollectionCreates the kV Store Collection.
- Create KV Store RecordCreates the kV Store Record.
- Create Local AppCreates the local App.
- Create LookupCreates the lookup.
- Create MacroCreates the macro.
- Create MessageCreates the message.
- Create PanelCreates the panel.
- Create RoleCreates the role.
- Create Saved SearchCreates the saved Search.
- Create Search JobCreates the search Job.
- Create TagCreates the tag.
- Create TCP InputCreates the tCP Input.
- Create TokenCreates the token.
- Create TransformCreates the transform.
- Create UDP InputCreates the uDP Input.
- Create UserCreates the user.
- Create ViewCreates the view.
- Create Workflow ActionCreates the workflow Action.
- Delete Event TypeDeletes the event Type.
- Delete Fired AlertDeletes the fired Alert.
- Delete HTTP InputDeletes the hTTP Input.
- Delete IndexDeletes the index.
- Delete KV Store CollectionDeletes the kV Store Collection.
- Delete KV Store RecordDeletes the kV Store Record.
- Delete Local AppDeletes the local App.
- Delete LookupDeletes the lookup.
- Delete MacroDeletes the macro.
- Delete MessageDeletes the message.
- Delete RoleDeletes the role.
- Delete Saved SearchDeletes the saved Search.
- Delete Search JobDeletes the search Job.
- Delete TagDeletes the tag.
- Delete UserDeletes the user.
- Disable Saved SearchPerforms the disable Saved Search operation.
- Dispatch Saved SearchPerforms the dispatch Saved Search operation.
- Enable Local AppPerforms the enable Local App operation.
- Enable Saved SearchPerforms the enable Saved Search operation.
- Get Alert ActionReturns the alert Action.
- Get ConfigReturns the config.
- Get Current ContextReturns the current Context.
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.
Frequently asked questions
Common questions about connecting Cortex and Splunk.
Connect your Cortex and Splunk 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]
Example: when Splunk's "Watch Fired Alerts" fires, WEXTL can "Delete Analyzer" in Cortex. Cortex has 13 actions (including Delete Analyzer, Delete Job, and Get Analyzer); Splunk has 148 actions (including Acknowledge Saved Search, Control Search Job, and Create Automatic Lookup). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Cortex-to-Splunk 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 Splunk) 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 + Splunk 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 Splunk integration.
- Cortex and Splunk integration source code, module specs and credentials implementation.
- Our Cortex and Splunk integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Cortex and Splunk — 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
- Splunk integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library