On this page
Project Setup

Configure a deployment trigger

Choose how your site redeploys after Acrosite commits content: Git-connected (your host builds from each commit), a Vercel, Netlify or Cloudflare Pages deploy hook, or Manual.

GuideFor Owners, Admins, DevelopersUpdated November 12, 2026

After Acrosite commits content to your repository, your site needs to rebuild so the change goes live. Most hosts rebuild on their own when the repository changes; otherwise a deployment trigger tells your host to redeploy. This guide sets up the right method.

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: from Git commits, from a deploy hook, or by hand.
  • If you want a hook, you have created one in Vercel, Netlify or Cloudflare Pages and copied its URL.

Choose a deployment method

From your project, open Deployment Setup in the sidebar and choose a method:

  • Git-connected (recommended) — your host already builds from the repository. Choose Save Git-connected Deployment; no URL is needed.
  • Vercel, Netlify or Cloudflare Pages — paste that host's deploy hook URL and choose Save Hook.
  • Manual — Acrosite commits content but nothing deploys automatically; choose Save Manual Deployment.
Important
Use a hook only when your host does not build from Git on its own. If it does, a hook makes every publish build twice. Choose Git-connected instead, or turn off the host's automatic Git builds for that branch.
Developer note
A deploy hook is a private URL that starts a build when it receives a request. Create one in your host's settings, then paste it here. Acrosite accepts only that host's hook address, 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 deploy hook is saved, 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. Git-connected and Manual have 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. With a hook, it then sends your deployment trigger; with Git-connected, your host builds from the commit. Each trigger is recorded in Deployment Logs, including the response status.

Acrosite triggers the deployment; a trigger does not mean the build finished. Owners and Admins see the build status your host reports to GitHub for each publish (Build status); if your host reports nothing, 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.
  • Every publish builds twice. Your host builds from Git and from the hook. Switch to Git-connected, or turn off the host's Git builds for that branch.
  • I do not use automatic deploys. Choose Manual and deploy on your own schedule.
  • My hosting provider is not listed. If it builds from your repository, choose Git-connected. Otherwise choose Manual and deploy yourself.