Integration
Connect Git to Blog Automation
For static sites (Hugo, Jekyll, Astro, Eleventy, Next.js): every article is written to your repository as a Markdown file with front matter, the cover image next to it - in a single commit.
What you need for Git
- A repository on GitHub, GitLab, Bitbucket, Gitea or Forgejo.
- An access token with write access to the contents of that repository.
- Optionally a deploy hook (Netlify, Vercel, Cloudflare Pages) so the site is rebuilt.
Step by step: connect Git
- Create an access token: GitHub → Settings → Developer settings → Fine-grained tokens (this repository only, "Contents: Read and write"); GitLab → project → Settings → Access tokens (role Developer, scope
api). - Bitbucket: Repository settings → Access tokens (Repositories: Write); Gitea/Forgejo: Settings → Applications (repository: read and write).
- In Blog Automation: Websites & blogs → Connect website → Git (GitHub, GitLab …). Enter provider, repository, branch and token, then click Check connection.
- Choose the site generator and, if needed, your own folders. Optionally add a deploy hook address, choose status and language and click Save.
Where do I find what in Git?
| Field in Blog Automation | Where to find it in Git |
|---|---|
| Repository | In the form owner/name, e.g. company/website. |
| Branch | Usually main. |
| Access token | See steps 1 and 2, e.g. github_pat_… or glpat-…. |
| Server address (only self-hosted GitLab, Gitea, Forgejo) | Your Git server’s address; leave empty for gitlab.com, github.com and bitbucket.org. |
| Deploy hook after the commit (optional) | Netlify: Site configuration → Build hooks; Vercel: Settings → Git → Deploy Hooks; Cloudflare Pages: Settings → Builds → Deploy hooks. |
What is transferred to Git?
The site generator decides the front matter keys and default folders, e.g. Hugo: content/posts and static/images, Jekyll: _posts/YYYY-MM-DD-slug.md, Astro: src/content/blog with pubDate and heroImage. With "Generic" you write your own template with placeholders such as {{title}}, {{date}}, {{tags}}, {{image}}.
Tips for Git
- Limit the token to the one repository.
- A failing deploy hook is only a warning - the commit stays.
Good to know about Git
- Drafts are files with
draft: true(Jekyllpublished: false) - whether your generator hides them depends on its settings. - Images inside the article text stay links; only the cover image goes into the repository.
- Without a deploy hook or automatic build the article only appears with the next build.
More in the official Git documentation (external link).
Frequently asked questions about Git
The check reports missing permissions.
The token needs write access to the contents (GitHub "Contents: Read and write") and must cover exactly this repository.
"Please enter "owner/name""
Enter the repository without https:// and without .git, e.g. company/website.
Ready for your first post?
Try Blog Automation with sample data
The demo opens at once, no sign-up needed. You see the dashboard, editor, calendar and approval just the way your team will use them.
The demo shows sample texts. The Free plan includes 200 tokens a month.