If your connected assistant has action permissions enabled, you can ask it to purge the Cloudflare cache for a domain. Say something like "purge the Cloudflare cache for example.com" and the assistant proposes the action, waits for your explicit yes, then runs it. You can do the same thing yourself any time in the portal under Goodies → Cloudflare CDN, using the Purge cache button next to the domain.
How the confirmation step works
Every action an assistant takes on your account, including a cache purge, goes through two steps: a proposal and a confirmation. Nothing changes until you say yes. If you say no or do not respond, nothing happens. This is the same pattern for any account change an assistant makes, not just cache purges. See Connect an AI assistant to your Flashcloud account for the full rundown of what assistants can and can't touch.
What actually gets cleared
A Cloudflare purge clears what Cloudflare has cached at the edge for that domain, so visitors get a fresh copy from your server. This matters after you push a code change, update a WordPress theme, or edit content that isn't showing up despite the underlying file being correct. It's a different layer from your server-side cache: if you're running WordPress, you likely also have LiteSpeed Cache and Redis object cache doing their own caching closer to the app. A Cloudflare purge doesn't touch those. If a page still looks stale after purging Cloudflare, clear the site's LiteSpeed Cache too, and remember your own browser can hold a cached copy as well.
Asking for it in plain language
You don't need to know any syntax. Reasonable phrasing works fine:
- "Purge the Cloudflare cache for example.com"
- "Clear Cloudflare's cache, I pushed a CSS update and it's not showing"
- "Is Cloudflare caching turned on for example.com, and can you purge it?"
The assistant can also check status first (whether proxy and caching are on for that domain) before proposing a purge, if you ask it to look before acting. If you haven't connected an assistant yet, the setup steps are the same regardless of which one you use: see Connect ChatGPT, Connect Gemini, or Connect an AI assistant.
Doing it without an assistant
If you'd rather skip the conversation, go to Goodies → Cloudflare CDN in the portal, find the domain, and click Purge cache directly. The same page has the proxy and caching toggles, SSL/TLS mode, and the rest of the per-domain Cloudflare settings, in case the caching behavior itself needs adjusting rather than a one-time clear.
If a purge doesn't fix it
If you've purged Cloudflare, cleared server-side cache, and the page still shows old content, the cause is usually somewhere else, a browser holding a cached copy, a CDN or proxy you don't control sitting in front of the request, or the change not actually having deployed yet. If everything checks out and the content is still stale, open a ticket from Support in the portal and a real person will dig into it with you.