Start a project

Vercel

Publish in the Studio. Vercel builds the site.

The client’s editor publishes the summer menu. Half a minute later, Vercel starts one build with it. You set it up once, with a deploy hook, and nobody in the client’s team ever opens Vercel.

Start a projectSee the integrations

Setup › Webhooks › Rebuild the site

{
  "name": "Rebuild the client site",
  "url": "https://api.vercel.com/v1/integrations/deploy/prj_…/…",
  "kind": "deploy",
  "batchSeconds": 30
}

Setup

Four steps, once

  1. Make the hook in Vercel

    In the project’s Settings › Git, under Deploy Hooks, give it a name and pick the branch to build.

  2. Paste it in the Studio

    Setup › Webhooks › Rebuild the site. Paste the address Vercel gave you, and save.

  3. Give the site its key

    In Vercel’s environment variables, add MOTEUR_KEY: a key that only reads the site’s channel.

  4. Publish something

    Change a title and publish. Watch Vercel’s deployments: one build, half a minute later.

Up close

What happens on publish

  • Builds

    One build for a busy morning

    Moteur waits half a minute after something goes live, in case more follows. Then it calls the hook once.

    • Entries, pages, menus, redirects, files
    • Tried again if Vercel doesn’t answer

    Setup › Webhooks › Rebuild the site

    {
  "name": "Rebuild the client site",
  "url": "https://api.vercel.com/v1/integrations/deploy/prj_…/…",
  "kind": "deploy",
  "batchSeconds": 30
}

  • Frameworks

    Next.js or Astro

    The hook doesn’t care what the site is built with. The code for each is on its own page.

    • Next.js: server components
    • Astro: frontmatter and getStaticPaths

  • Refresh

    Or no build at all

    With Next.js, a signed webhook can refresh just the pages that changed. No build, nothing to wait for.

    • Your route checks the signature
    • Then refreshes what you choose

  • Previews

    Drafts on the real site

    The Studio opens the client’s site at its preview address. One route, rendered on request on Vercel, shows the draft. The rest stays static.

    • The link lasts half an hour
    • Without it, the page shows what’s live

Questions about Vercel

An agency owner asksDoes every save start a build?

MoteurNo. Only what goes live: an entry, a page, a menu, a redirect or a file. Saves of drafts don’t touch Vercel.

An agency developer asksWill a busy client run into Vercel’s limits?

MoteurUnlikely. Vercel takes up to 60 hook calls an hour per project, by its own documentation, checked 27 October 2026. Moteur gathers what goes live within half a minute into one call. A client would have to publish more than once a minute, for an hour, to reach it.

An agency developer asksCan we build a staging branch too?

MoteurYes. A Vercel hook builds one branch. Make a second hook for staging, and add it as a second webhook in the Studio.

An agency owner asksDo we have to use Vercel?

MoteurNo. Netlify and Cloudflare Pages work the same way, with their own build hooks.

Keep reading

Connect your next client site to Vercel.

Start for free, paste a deploy hook, and publish something.

Start a project