Publish requested compliance DNS verification records
Handle a specified DNS verification request on schedule, with the record details confirmed before anything is created.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
A verification record can be a small but time-sensitive compliance task that gets missed while teams move between their audit and DNS tools.
- Check for a specified verification request on a recurring schedule.
- Create a DNS record only when the request includes a confirmed zone, record name, type, and content.
- Get a run report for review and follow-up.
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: check for the specified verification request and create its DNS record only when the zone, name, type, and content are confirmed.
- 4Pick a recurring Notis schedule and choose where run reports should go.
- 5Test with one real verification request and confirm the new record in Cloudflare.
Questions about this workflow
Can this publish any DNS record type?
The Cloudflare action supports record types such as A, CNAME, TXT, and MX. The request needs to supply the intended type and record details.
Will the schedule scan every 21risk task?
The instruction should identify the specific kind of verification request to check. 21risk has no trigger events here, and the workflow should not treat unrelated tasks as DNS requests.
What happens if the request is incomplete?
The automation should report what is missing and skip creating the record until the required details are available.
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.