Apply approved IP lockdown actions from 21risk
Put an approved access restriction into effect without retyping its details across compliance and Cloudflare.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Compliance actions can be approved in one place and still sit unfinished while someone looks up the Cloudflare zone and recreates the restriction.
- Convert an explicitly approved action into a Cloudflare lockdown rule.
- Keep the URL pattern and allowed IP ranges tied to the compliance request.
- Avoid creating a rule when the request lacks a confirmed zone or required details.
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: create a Zone Lockdown rule only for an approved 21risk action with a confirmed zone, URL pattern, and IP or CIDR ranges.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real approved action and verify the resulting rule in Cloudflare.
Questions about this workflow
Does 21risk trigger this automation directly?
No. 21risk has no exposed trigger events in this setup. A Notis webhook starts the automation, and the instruction can use the supplied request context and connected app data.
What details are needed to create the rule?
The request needs an approved action, a confirmed Cloudflare zone, URL patterns, and IP addresses or CIDR ranges. Notis should ask for missing information instead of guessing.
Will it create a lockdown rule for a draft or unapproved finding?
The automation instruction should require explicit approval before it creates the rule.
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.