Cloudflare integration
Manage Cloudflare DNS, domains and certificates in one place
Connect your Cloudflare account and every zone, record, domain and certificate it holds appears in InfraNest — in the same lists as the ones you keep at every other provider. Edit a record, check an expiry date or purge the cache without opening the Cloudflare dashboard.
Free plan · About 3 minutes · You choose what the token is allowed to do
- Zones and records imported the moment you connect
- DNS in plain English, not a wall of acronyms
- Domain and certificate expiry dates in one list
- Cache and security changes on a trigger
7 records at Cloudflare · read from the provider 12m ago · resolvers checked 7m ago
The website5 record(s)
Email1 record(s)
Verification1 record(s)
A2 record(s)
AAAA1 record(s)
CNAME2 record(s)
TXT2 record(s)
Edit Cloudflare DNS without opening Cloudflare
Connect the account and every zone you have at Cloudflare is found and imported — there is nothing to re-enter. From then on those records live in the same editor as the records you keep everywhere else: create them, change them, delete them, proxied setting included. The editor groups each zone by what the records actually do — the website, email, everything else — so you can see which rows keep the site up and which keep mail flowing, instead of reading a column of acronyms and hoping.
- Create, edit and delete records in any Cloudflare zone, proxied setting included
- Existing zones and their records imported automatically when you connect
- Grouped by purpose — the website, email, everything else
- One editor for Cloudflare and every other DNS provider you use
- Monitor App — northwyndr-app.dev checks this name. After the change it checks whatever the new value answers.
- Certificate northwyndr-app.dev covers this name. Its renewal has to reach the new target.
- app.northwyndr-app.dev follows this record and changes with it.
- api.northwyndr-app.dev follows this record and changes with it.
- Cloudflare nameserversNew address
- Cloudflare public DNSNew address
- Google public DNSOld address, for up to 4 more minutes
Domains registered at Cloudflare, in the same list as the rest
Names you bought at Cloudflare sit next to the ones you bought anywhere else, with expiry date, auto-renew and transfer lock as columns you can sort. Change auto-renew, WHOIS privacy or the transfer lock without a separate login, pull the transfer code when a name needs to move, and hear about a renewal date long before it arrives rather than the week after it passed.
- Expiry, auto-renew and transfer lock in one sortable list
- WHOIS privacy, auto-renew and transfer lock changed without logging in to Cloudflare
- The transfer (EPP) code for a Cloudflare-registered domain, on the page
- Renewal warnings across every registrar you use, not just this one
Cloudflare certificates, with expiry dates you can actually see
Certificates issued through Cloudflare appear in your certificate list with their expiry dates, instead of being checked one zone at a time — beside the ones your servers issued themselves and any you uploaded by hand. They are then watched like the rest: you are told when one is expiring, weak, revoked, or simply not the certificate that was supposed to be there.
- Cloudflare certificates listed with their expiry dates, not checked zone by zone
- Warned about certificates that are expiring, weak, revoked or unexpected
- One list for every source — Cloudflare, your servers, manual uploads
- The hostnames each certificate actually covers, spelled out
Purge the cache or raise the security level from a rule
Four Cloudflare controls are available as steps in a rule rather than as things you have to remember: purge the cache, turn development mode on or off, adjust always-online, and change the security level. What sets them off can come from anywhere else you have connected — a DNS record that changed, a certificate getting close to expiry, a domain renewing. You build the rule by choosing when it runs and what it should do, and nothing happens until you switch it on.
- Purge cache, development mode, always-online and security level as rule steps
- Started by DNS, certificate or domain events from any provider you connect
- No scripts: pick a trigger, add the steps, read it back in plain English
- Nothing runs until you turn the rule on — see how rules are built
When this happens
A domain is approaching its expiry date.
Domain expiring
A domain is approaching its expiry date.
Runs at 09:00 · Europe/Amsterdam · it’s 16:16 there now
Next runs:Tue 3 Nov, 09:00Wed 4 Nov, 09:00Thu 5 Nov, 09:00
This automation only runs when you click “Run now”.
Only if — optional filters
MatchAllAnyNoneof these conditions
Tip: a value can reference another field or the time using a placeholder.
Do this — actions run in order, stop at the first failure
In plain English
When Domain expiring if Days left less or equal 15, then Require approval, Set auto-renew and Send notification.
Choose a trigger and an action to see a live summary.
Test it
Conditions pass — this would run
1 of 1 matchedConditions fail — this would not run
0 of 1 matchedRuns each step in dry-run against a real example from your account — nothing is changed.
1. Require approval
Would pause for approval
2. Set auto-renew
domain has no registrar connection
3. Send notification
Would notify 1 destination(s)
dry run
Choose a trigger and at least one action first.
See your own Cloudflare zones in InfraNest
Free plan, no credit card. Connect the account and your zones, records and domains appear on their own.
Connect Cloudflare in about three minutes
One API token, created in your own Cloudflare account. You decide what it may do there — give it read access first if you would rather look around before anything can be changed.
- 1
Open the Cloudflare integration
Go to Integrations and open Cloudflare to start the connection.
- 2
Choose your features
Pick which of DNS, Domains and Certificates you want InfraNest to manage.
- 3
Connect your account
Use one-click connect, or paste an API token with the right permissions, then select Connect — your zones are imported automatically.
That’s it — Cloudflare is connected.
Full setup guideSet up with AI
I want to connect my Cloudflare account to InfraNest (infranest.io), which manages DNS, domains and certificates across providers. Walk me through creating a Cloudflare API token with these permissions: Zone: Read, DNS: Edit, Cache Purge: Purge, Zone Settings: Edit, Domain Registrar: Admin, and SSL and Certificates: Read. For each one, tell me where it is in the current Cloudflare dashboard, what it allows, and whether I can leave it out if I only want to manage DNS records at first. Then tell me how to check the token works before I paste it anywhere.
What syncs
What InfraNest keeps in sync with Cloudflare.
| DNS zones | DNS zones and records |
| Domains | Domains, expiry dates, nameservers and lock state |
| Certificates | Certificates and their expiry |
What still happens in Cloudflare
InfraNest can't register brand-new domains or transfer domains into Cloudflare — new registrations and incoming transfers are done on Cloudflare's own site. Cloud resources also aren't covered by this integration.
MCP server
Cloudflare in Claude and ChatGPT
Connect your AI assistant to InfraNest and ask about your Cloudflare account in plain words, next to every other provider you use. It reads, and acts only when you allow it.
- Which of my Cloudflare domains expire in the next 60 days?
- Where does shop.example.com point, and did anything change there this week?
- Which certificates expire this month, and does anything renew them?
Often connected together
Questions about the Cloudflare integration
#Will connecting Cloudflare change my existing DNS setup?
No. Connecting only imports your existing zones and records so you can see and manage them from InfraNest. Nothing changes until you make an edit yourself.
#Can I manage more than one Cloudflare account?
Yes, you can connect multiple Cloudflare accounts at once and they stay distinguishable by the account label you give each one.
#What happens if my API token is revoked or expires?
InfraNest will show the connection as failing and pause the affected features until you update the credential. Reconnecting with a fresh token or signing in again picks up right where you left off.
#Can InfraNest change settings on my Cloudflare account, or just read them?
Both. With the right permissions, InfraNest can edit DNS records, purge the cache, toggle Always Online or Development Mode, change the security level, and manage domain settings like auto-renew and transfer lock, not just display them.
#What do I need before connecting Cloudflare?
You need a Cloudflare API token with the Zone, DNS, Cache, Zone Settings, Domain Registrar and SSL/Certificates permissions (or use one-click connect instead) — see the setup guide.
#Is there a Cloudflare MCP server?
Yes, through InfraNest. Once Cloudflare is connected, InfraNest’s MCP server lets Claude, ChatGPT, Cursor, VS Code and other assistants read your domains, DNS records and certificates at Cloudflare, together with every other provider you use. It works on every plan, including Free. Cloudflare also runs its own MCP server for your Cloudflare account alone. InfraNest’s answers across all your providers, with your monitors and incidents in the same answer.
Bring Cloudflare into one dashboard
Connect it in about three minutes, then add the next provider. Everything you run, in one place.
Free plan · No credit card required · Set up in minutes