Developers

Integrations

Patterns for fitting Webforgia into the rest of your stack.

An AI assistant that builds for you

Connect Claude, Cursor or VS Code to the MCP server with a key scoped to read and write, and keep publish for a person. The assistant drafts; you review and press Publish.

Leads into anything

Point the Webhook connector at Zapier, Make, n8n or your own endpoint, and route each lead wherever your team works. For a CRM or sheet Webforgia supports directly, use its connector instead — no middleman.

Builds from your own systems

Call the build API from a script or CI job — for example, a landing page per product from your catalogue. Keep the key in a secret, and set save: false if you only want the specification.

Code in your repository

Push sites to GitHub, or have GitLab receive a commit on every publish, and deploy them with your own pipeline. See Self Hosting for what changes when you host them yourself.