Connect GitHub to Inflowave
Already have a website? Connect its GitHub repo instead of rebuilding it.
What this integration does
Inflowave's Websites product can build a site from scratch with AI, or it can run on a GitHub repository you already have. Connecting a repo installs Inflowave's GitHub App on the repos you choose, through GitHub's own consent screen - we're never shown your GitHub password. You pick one of two access tiers up front: deploy-only, where Inflowave clones your repo, runs your own build, and hosts the output with nothing ever written back to GitHub; or full edit, which adds Inflowave's visual editor on top of your code, with every change opened as a pull request on your repo rather than pushed directly. Either way, the repo stays yours. Once connected, a push to your branch triggers an automatic rebuild and redeploy, the same way push-to-deploy works on Netlify or Vercel.
How to connect - 5 steps
- 1
In Websites, start a new site via 'Connect your repo' instead of the AI builder
- 2
Choose deploy-only (hosting only) or full edit (visual editor, changes come back as a PR)
- 3
On GitHub's install screen, grant access to the specific repository or repositories you want
- 4
If you granted more than one new repo, pick which ones should become websites
- 5
Hit Build & Deploy to publish - nothing goes live automatically on import
Use cases
Host a site you already built
Skip rebuilding a hand-coded or developer-maintained site in Inflowave's AI builder - connect the repo and host it as-is.
Let a developer keep the code, let the client edit the copy
Full-edit access gives a non-technical client a visual editor while every change still shows up as a reviewable pull request for the developer.
Push-to-deploy from your own workflow
Keep committing to your repo the way you always have - Inflowave rebuilds and redeploys automatically on every push.
Why agencies choose Inflowave + GitHub
- Nothing is copied out of GitHub into a separate repo you don't control
- Deploy-only access never writes to your repository at all
- Full-edit changes arrive as a pull request, never a direct push or force-push
- Automatic rebuilds on every push, with no manual redeploy step
- Disconnecting only unlinks the site - your repo and your live site are both left untouched
Frequently asked questions
Does this copy or fork my code?
No. Inflowave builds directly from your repo through GitHub's own App-install flow. Nothing is duplicated into a repository you don't control.
Will Inflowave push directly to my repo?
Only with full-edit access, and only as a pull request - never a direct push to your default branch. Deploy-only access never writes to your repo at all.
Can I connect a repo to a site I already built with the AI builder?
No - connecting a repo is a new-site flow and won't retrofit an existing AI-built project.
How do I fully revoke access?
Disconnecting in Inflowave only unlinks the repo from your site. To revoke the grant itself, remove the Inflowave App from your installed GitHub Apps in your GitHub account settings.
How GitHub works with Inflowave in practice
The GitHub integration plugs into the same Inflowave workflow engine that handles DM automation, lead pipelines, and unified inbox. Connect an existing GitHub repository to Inflowave. Import a site you already have, deploy it as-is, or edit it visually with changes that come back as a pull request. Once connected, every event GitHub fires can trigger an Inflowave automation - and every Inflowave action can write data back into GitHub - so the two tools stay in sync without manual exports or copy-paste.
Most teams using Inflowave alongside GitHub land on a similar setup pattern: connect the account on the integrations page, pick the events you want to react to, and route the data into the Inflowave entity it should live on (lead, contact, conversation, or pipeline stage). Setup takes about 10 minutes for a fresh workspace and is reversible - disconnecting cleanly removes the webhook and stops the data sync.
Inflowave's role is to be the CRM agencies run their clients on - which means the GitHub integration's value lands hardest when there's a real conversation flow to attach data to. Agencies running multiple client workspaces use GitHub per-client; a single business tends to wire one GitHub account to all of its connected channels. Both shapes are supported by the same integration code path.
If GitHub isn't the right fit, Inflowave ships native equivalents for many common workflows (built-in scheduling, built-in CRM, built-in unified inbox), so the integration is meant for teams that already standardized on GitHub and want to keep using it - not as a gating dependency. The integration is included in every paid Inflowave plan with no per-event surcharge.
Connect GitHub in 60 seconds
7-day free trial. Up to 50 Instagram accounts. Cancel any time.