STEP 1
Connect Cloudflare and Cortex
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Cloudflare and Cortex Integration
Keep Cloudflare and Cortex in sync by integrating their events and actions. When developer tools events happen in Cloudflare, update the Cortex 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 Cloudflare and Cortex
Detailed info you need to know about Cloudflare and Cortex integrations in WEXTL. Explore which modules apps support and how you connect them.
Cloudflare
Cloudflare edge platform — zones, DNS, caching, Workers, R2, Zero Trust, and account management. [5]
How to connect Cloudflare to Cortex
Set up your Cloudflare and Cortex integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Cloudflare and Cortex 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 Cloudflare and Cortex. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Cloudflare and Cortex work in WEXTL?
WEXTL exposes actions and triggers for Cloudflare and Cortex 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.
Cloudflare triggersCortex actions
Cloudflare modules
- Watch Audit LogsTriggers when a new audit log entry is recorded on the account.
- Account DetailsRetrieves an account's details.
- Create a NamespaceCreates a new Workers KV namespace.
- Create an AccountCreates a new account under a tenant.
- Create An IP Access RuleCreates a new IP Access rule.
- Create BucketCreates a new R2 bucket.
- Create Cloudflare TunnelCreates a new Cloudflare Tunnel.
- Create DNS RecordCreates a new DNS record.
- Create Firewall RulesCreates new firewall rules.
- Create Health CheckCreates a new health check for a zone.
- Create Load BalancerCreates a new load balancer.
- Create MonitorCreates a new load balancer monitor.
- Create PoolCreates a new load balancer pool.
- Create RouteCreates a new Worker route.
- Create SSL ConfigurationUploads a new custom SSL certificate.
- Create Tunnel RouteCreates a new private network route for a tunnel.
- Create ZoneCreates a new zone.
- Create Zone RulesetCreates a new zone ruleset.
- Create Zone Ruleset RuleAdds a rule to a zone ruleset.
- Delete A Firewall RuleDeletes a firewall rule.
- Delete an AccountDeletes an account.
- Delete An IP Access RuleDeletes an IP Access rule.
- Delete BucketDeletes an R2 bucket.
- Delete Cloudflare TunnelDeletes a Cloudflare Tunnel.
- Delete DNS RecordDeletes a DNS record.
- Delete Health CheckDeletes a health check.
- Delete Load BalancerDeletes a load balancer.
- Delete MonitorDeletes a load balancer monitor.
- Delete ObjectDeletes an object from an R2 bucket.
- Delete Objects or Empty BucketDeletes multiple objects or empties a bucket.
- Delete PoolDeletes a load balancer pool.
- Delete RouteDeletes a Worker route.
- Delete SSL ConfigurationDeletes a custom SSL certificate.
- Delete WorkerDeletes a Worker script.
- Delete ZoneDeletes a zone.
- Delete Zone RulesetDeletes a zone ruleset.
- Delete Zone Ruleset RuleRemoves a rule from a zone ruleset.
- DNS Record DetailsRetrieves a DNS record's details.
- Download WorkerDownloads a Worker script's content.
- Edit Multiple Zone SettingsUpdates multiple zone settings at once.
- Edit Universal SSL SettingsUpdates a zone's Universal SSL settings.
- Edit ZoneUpdates a zone's paused state, plan, or type.
- Edit Zone SettingUpdates a single zone setting's value.
- Enable Worker SubdomainEnables a Worker's workers.dev subdomain.
- Get a NamespaceRetrieves a Workers KV namespace's details.
- Get All Zone SettingsRetrieves all settings for a zone.
- Get BucketRetrieves an R2 bucket's details.
- Get Certificate PackRetrieves a certificate pack's details.
- Get Cloudflare TunnelRetrieves details for a Cloudflare Tunnel.
- Get ObjectDownloads an object from an R2 bucket.
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.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Cloudflare and Cortex integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Cloudflare and Cortex.
Connect your Cloudflare and Cortex 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 Cloudflare's "Watch Audit Logs" fires, WEXTL can "Delete Analyzer" in Cortex. Cloudflare has 1 trigger (including Watch Audit Logs); Cortex has 13 actions (including Delete Analyzer, Delete Job, and Get Analyzer). 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. Cloudflare-to-Cortex 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 Cloudflare (or Cortex) 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 Cloudflare + Cortex 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 Cloudflare and Cortex integration.
- Cloudflare and Cortex integration source code, module specs and credentials implementation.
- Our Cloudflare and Cortex integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Cloudflare and Cortex — 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.
- Cloudflare integration information
- Cortex integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library