Give Chat4U automation access to your Vercel project

What you’ll accomplish

Create an automation token in the correct Vercel project, enter it in the affected Chat4U source, then verify the import.

Finish with

A dedicated Vercel token and verified website content

Create the token in Vercel

1. Open the correct project's protection settingsCheck which project serves the affected hostname.

   In your Vercel dashboard, select the project, then open Settings → Deployment Protection. Find Protection Bypass for Automation. If you cannot access it, ask the project's administrator to do this step; do not create a token for a different project. Vercel's setup instructions.

2. Create a dedicated secretGive Chat4U access that you can revoke independently.

   Select Create and use a descriptive label such as Chat4U website import. Copy the generated secret privately for the Chat4U field. Keep it out of website URLs, screenshots, shared reports and source code. Follow any deployment update requirement Vercel shows when changing or regenerating an existing secret.

Configure the affected Chat4U source

In Project → Knowledge, open the affected source's access dialog. Choose Website access token, select Vercel automation bypass, enter the secret, select Save settings, confirm you are authorized, then select Test access and retry import. Chat4U uses the x-vercel-protection-bypass header; do not append the token to the source URL. The header name is selected by the Vercel preset.

If access is still refused

1. Check that the affected hostname/deployment belongs to the project where you created the token.
2. Confirm the Vercel preset was selected and the entered value is an active secret from that project's protection settings. A renamed label is not the secret value.
3. If the secret was regenerated or removed, follow Vercel's redeployment requirement and update Chat4U to the current value. Retest the current settings.
4. Read the latest Chat4U explanation and ask the administrator to inspect the matching request. Active-attack mitigations can still refuse a valid token; another login/security layer may also be responsible. Token scope and remaining protections.

If you cannot create a secret or grant the required access, send the safe administrator report and this guide, or import a file/text alternative. A public User-Agent identifier does not substitute for Vercel's secret.

Replace or remove access

Revoke only the dedicated Chat4U secret when access is no longer needed, then remove it from the source. For replacement, create/update the dedicated secret, follow Vercel's deployment instructions, enter the matching new value in Chat4U and check again. Existing imported content is separate from future website access.

Last updated on