Cortex
Run Cortex analyzers and responders on observables and read the jobs they produce.
OCNORA ships 8 typed Cortex operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Cortex
- Authentication
- Bearer token
- Credential
- the Cortex organisation API key, or {"api_key": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Cortex
Operations, grouped by what they do to your data.
Create and send 2
Read and search 4
Delete and cancel 1
Other operations 1
A sample Cortex workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Cortex trigger is needed.
- 2Get Job Reportcortex.get_job_reportFetch a job with whatever report it has right now.
- 3Delete Jobcortex.delete_jobMark a job deleted so it stops appearing in listings.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Delete JobMark a job deleted so it stops appearing in listings.cortex.delete_job
- Get Job ReportFetch a job with whatever report it has right now.cortex.get_job_report
- List AnalyzersList the analyzers enabled for the connection's organisation.cortex.list_analyzers
- List JobsList the jobs the connection's user can see, newest first.cortex.list_jobs
- List RespondersList the responders enabled for the connection's organisation.cortex.list_responders
- Run AnalyzerSubmit one observable to an analyzer and return the queued job.cortex.run_analyzer
- Run ResponderSubmit a record to a responder and return the queued job.cortex.run_responder
- Wait For Job ReportHold the request open until a job finishes, then return its report.cortex.wait_job_report
Cortex questions
- How does OCNORA authenticate with Cortex?
- With a stored Bearer token credential, shaped the Cortex organisation API key, or {"api_key": "…"}. A connection test can check it when you add it.
- What can I automate with Cortex?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Cortex operation I need is not listed?
- Where Cortex has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Cortex?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Cortex calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first Cortex workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.