Docs
Start building
Developers

Connectors

Connectors from a developer's point of view: where data flows, and the ones built for developer workflows.

Where data flows

  • Lead connectors receive a copy of each form submission after it is saved. A failure in one never affects another or the submission.
  • Site connectors change the published output — a link, a head tag, server-side page-view forwarding — and take effect on the next build or publish.
  • Build connectors run while Webforgia builds or publishes: reading a site to import, querying data, deploying, committing or backing up.

Credentials are stored encrypted, checked with the provider when you connect, and never returned to the browser. Outbound calls are refused to private and internal addresses.

For developer workflows

Cloud

Built-in backend, ready to use

Always on

Hosting, forms and storage for everything you publish. Always on.

Webhook

POST form leads to any URL

Receives form leads

POSTs every new form lead to your URL as JSON. We send one test event when you connect.

You provide: Webhook URL (stored encrypted)

GitHub

Repos, issues, and CI

Connects your accountBeing set up

Push your website's code to a GitHub repository. Connected in Settings → Git.

Connects by signing in to GitHub; nothing to paste.

GitLab

Repos and pipelines

Used while building

Every time you publish, your site's files are committed to your GitLab project.

You provide: Access token (stored encrypted), Project path or link

Where to find it: GitLab → Preferences → Access tokens → scope api, role Developer or above.

Supabase

Postgres backend & auth

Receives form leads

Inserts every new form lead as a row in your Supabase table.

You provide: Project URL, API key (stored encrypted), Table

Where to find it: Columns: kind, name, email, message, site (text) and created_at (timestamptz default now()). With RLS on, add a policy allowing INSERT for anon.

Sentry

Error monitoring

Used while building

Reports your sites' failed form deliveries and publish errors to your Sentry project.

You provide: DSN (stored encrypted)

Where to find it: Sentry → Project settings → Client Keys (DSN).

Vercel

Deployments and hosting

Used while building

Every time you publish, your website is also deployed to your Vercel project.

You provide: Access token (stored encrypted), Project name

Where to find it: vercel.com/account/tokens → create a token scoped to the team that owns the project.