Introduction
Cloudflare Browser Rendering loads web pages in a real browser and returns their text. As the web page reader, it gets the content of pages built with JavaScript, which often come back empty when read directly.Setting up
1
Find your account ID
Your account ID is shown on the Account home page of the Cloudflare dashboard, and in the address after
dash.cloudflare.com/.2
Create an API token
Open API Tokens and create a custom token with the Browser Run - Edit permission (Browser Rendering - Edit on older dashboards).
3
Add them to Aikeedo
Go to Settings → Integrations → Cloudflare, enter the Account ID and API Token under Browser Rendering, and click Save changes.
4
Choose it as the web page reader
In Settings → Features → Chat, under Web browsing, choose Cloudflare as the Web page reader. Leave Use only as fallback on to send only the pages your server can’t read.
Plans and limits
- Workers Free plan: Cloudflare reads one page every 10 seconds. Pages over that limit are read on your server instead.
- Billing: Cloudflare bills browser time beyond the hours your plan includes.
The Queue Adapters plugin can use the same account. If you leave its account ID and token empty, it uses these, and the token then also needs the Queues permission.
Troubleshooting
Pages are still read on the server
Pages are still read on the server
With Use only as fallback on, Cloudflare is used only for pages your server can’t load or reads too thin. On the Workers Free plan, pages over the rate limit are also read on your server.
Requests fail with an authentication error
Requests fail with an authentication error
Check that the token has the Browser Run - Edit permission and belongs to the account ID you entered.
Need Help?
If you need assistance with Aikeedo:Professional Support
Get expert help from our team with a paid support subscription
Troubleshooting Guide
Check common issues and solutions