Add approved compliance rules to an existing ruleset
Carry an approved security requirement into the Cloudflare ruleset where it belongs, with the ruleset and rule details confirmed first.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Rule in Ruleset
Tool to add a rule to an existing ruleset. Use when you need to append or insert a new rule in a Cloudflare ruleset.
Why this helps
Approved security requirements can be hard to translate into the right existing ruleset when the compliance context and Cloudflare configuration live in separate tools.
- Use a 21risk action as the starting point for an approved Cloudflare rule change.
- Require a confirmed ruleset and complete rule details before making a change.
- Send a run report so the change is easier to review.
Setup
Build it in a few focused steps.
- 1Connect 21risk and Cloudflare api key once in the Notis portal.
- 2Create an automation in the portal, or tell Notis to create one, and give it a clear name.
- 3Describe the outcome in one instruction: add a rule only for an explicitly approved action when the target ruleset and complete rule details are confirmed.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real approved action and review the rule in the intended Cloudflare ruleset.
Questions about this workflow
Does this create a ruleset too?
No. This workflow adds a rule to an existing ruleset. Creating a ruleset is a separate Cloudflare action and requires defining its details and scope.
Can Notis infer the rule expression from a general compliance finding?
The request or connected data needs to provide the required rule details. The automation should not invent an expression or ruleset.
What starts the workflow?
A Notis webhook starts it. 21risk does not expose a trigger event here.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Cloudflare api key. A trigger fires from one place; an action lands in another.
21risk triggers
Cloudflare api key actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create DNS Record
Tool to create a new DNS record in a Cloudflare zone. Use when you need to add a record (A, CNAME, TXT, MX, etc.) to a specified zone.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Zone Lockdown Rule
Tool to create a Zone Lockdown rule. Use when you need to restrict access to specific URL patterns to defined IPs/CIDR ranges. Use after confirming zone_id.
Create Rule in Ruleset
Tool to add a rule to an existing ruleset. Use when you need to append or insert a new rule in a Cloudflare ruleset.
Create Ruleset
Tool to create an account- or zone-scoped ruleset. Use after defining your ruleset details and selecting the correct scope.
Delete DNS Record
Tool to delete a DNS record. Use when you need to remove a specific DNS record from a zone after confirming both zone and record IDs.
Delete DNSSEC
Tool to delete DNSSEC records for a zone. Use after disabling DNSSEC at the registrar to remove DNSSEC configuration.
Delete Rule from Ruleset
Tool to delete a specific rule from a ruleset. Use when you need to remove an outdated or incorrect rule from an account or zone ruleset after confirming IDs.
Delete Ruleset
Tool to delete all versions of a ruleset. Use when you need to remove a ruleset from an account or zone after confirming no references exist.
Connect any two apps with Notis in the middle.
21risk and Cloudflare api key, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Cloudflare api key.