Configure a deployment trigger

Choose how your site redeploys after Acrosite commits content. Connect a Vercel deploy hook, or choose Manual / No Automatic Deployment. Other providers appear as Coming Soon and cannot be configured yet.

GuideFor Owners, Admins, DevelopersUpdated June 7, 2026

After Acrosite commits content to your repository, your site needs to rebuild so the change goes live. A deployment trigger is how Acrosite tells your hosting provider to redeploy. This guide sets one up.

Who this is for

Workspace Owners, Admins, and Developers. Finding a deploy hook URL usually requires access to your hosting provider's settings.

Before you start

You have connected GitHub for the project. See Connect GitHub.
You know how your site deploys today (Vercel, or another provider you deploy yourself).
If you deploy on Vercel, you have created a deploy hook there and copied its URL.

Choose a deployment method

From your project, open Deployment Setup in the sidebar. Two methods are available today:

Vercel Deploy Hook — paste your Vercel deploy hook URL.
Manual / No Automatic Deployment — Acrosite commits content but does not trigger a deploy; you deploy yourself.

Netlify, Cloudflare Pages, GitHub Actions, Custom Webhook, Render, DigitalOcean App Platform, AWS Amplify, GitHub Pages, and Firebase Hosting appear as Coming Soon and cannot be configured yet.

Select the method that matches your setup, enter its details, and save. For the manual option, choose Use Manual Deployment.

Developer note

A deploy hook is a private URL that starts a build when it receives a request. Create one in Vercel, then paste it here. Acrosite stores it securely and never shows the full URL again — only the last few characters, so you can recognise it.

Test the trigger

Once a Vercel Deploy Hook is configured, use the Test Deployment Trigger action. Acrosite sends a test request and records the response, so you can confirm the connection works before you publish real content. Manual / No Automatic Deployment has no trigger to test.

Important

A successful test confirms your provider accepted the request. It does not confirm the build finished — check your provider's dashboard for build status.

What happens next

From now on, each time content publishes, Acrosite commits the files and then sends your deployment trigger. Each trigger is recorded in Deployment Logs, including the response status.

Acrosite triggers the deployment — it does not track the build to completion. If you need to confirm the live site updated, use your hosting provider's dashboard.

Troubleshooting

The test failed. Re-copy the deploy hook URL from your provider; hooks can be regenerated or revoked. Make sure the URL is complete and uses https://.
My site builds but content is missing. Confirm GitHub is connected and the commit succeeded in Publish Logs, and that your site reads content from the paths Acrosite writes to.
I do not use automatic deploys. Choose Manual / No Automatic Deployment and deploy on your own schedule.
My hosting provider is not listed. Hosting providers other than Vercel appear as Coming Soon and cannot be configured yet, so choose Manual / No Automatic Deployment for now.

PreviousAcrosite-managed content paths NextTest your deployment trigger