Connect a client's website to GitHub

If you're a TrustPager agency, you can build your clients' websites in your own GitHub repos, with Claude Code or any other tool, and host them on TrustPager. Every push builds a preview you can check, and one click makes it the live site. Everything happens at https://app.trustpager.com/agency/websites.

If that page says connecting GitHub isn't switched on yet, it's on its way. Everything below works as soon as it is.

1. Connect GitHub (agency owner, once)

1. Go to https://app.trustpager.com/agency/websites and click Connect GitHub at the top right.
2. On GitHub, choose your account or organisation, and choose which repos TrustPager can see. You can pick just the repos for your clients' sites.
3. GitHub brings you back to TrustPager, and your GitHub account shows as connected.

The app only reads the repos you choose. When the AI website editor changes a site, it sends the change to you as a pull request. TrustPager never pushes to your branches. To connect a second GitHub account or organisation, click Add a GitHub account.

2. Connect a repo to a client

1. On https://app.trustpager.com/agency/websites, find the client and click Connect repo.
2. Choose the repo and the branch to publish from (usually main).
3. Leave Publish automatically off if you want to check each preview first.
4. Click Connect repo.

If the client has no website yet, one is set up for them at the same time. Hosting is $5 a month, charged to the client's own workspace. TrustPager works out how to build the site from its package.json. For anything unusual, open Build settings and set the build command and the output folder yourself.

3. Push, check the preview, publish

Each push to the connected branch builds a preview. Pushes close together are built once, about two minutes after the last one. When the preview is ready, the client's row shows Preview ready and a Preview link. Check it, then click Publish to make it the live site.

Turn on Auto-publish for a client and every preview that builds goes live straight away, with no Publish click. Sync now builds the branch's latest commit again, and Disconnect stops pushes reaching the site (the live site stays as it is).

When a build fails

The client's row shows Failed and the end of the build log, which says what went wrong. Fix it in your repo and push again. If you work with Claude, give it the log.

What's copied, and the limits

• Files that look like secrets, such as .env files and keys, are never copied. The page lists anything that was left out. Keep secrets out of your repos.
• Server code isn't allowed: a push with a functions folder or a _worker.js file is refused. Sites are static.
• Each repo can have up to 2,000 files and 50 MB. Leave build output and installed packages out of the repo.
• Your agency can build 20 times a day across all its clients. Each preview and each publish counts as one.

Domains

Once a client's site is set up, open Domain under the client on https://app.trustpager.com/agency/websites to point their domain at it. You'll see the DNS records to add at their DNS provider, and the domain's status.

Checking from your own tools

An agency API key with Agency access can list your clients' websites, the repo each is built from, and their latest syncs and build errors. See the agency API key section of https://app.trustpager.com/training/help-center/agency-guide.

Need a hand? Submit a service request at https://app.trustpager.com/settings/service-requests.