# Integrations overview

Connect formbase to scheduling, analytics, spreadsheets, messaging, project tools, and custom webhooks.

## Connect your workflow

Schedule appointments, stream analytics, deliver submissions, and connect formbase to tools your team already uses.

<h2 id="three-models">Three connection models</h2>

<p>
  Integration setup differs by feature. Knowing which model you are using explains where configuration lives and what starts happening after
  you connect.
</p>

<h2 id="available">Available connections</h2>

<div class="not-prose grid gap-3 sm:grid-cols-2">
  - [Cal.com](/integrations/cal-com) — Book appointments inside forms
  - [Analytics streaming](/integrations/analytics-streaming) — Send events to GA4 or Axiom
  - [Google Analytics (GA4)](/integrations/google-analytics) — Add form events to your GA4 property
  - [Axiom](/integrations/axiom) — Query events and optional respondent answers
  - [Google Sheets](/integrations/google-sheets) — Append submissions to a spreadsheet
  - [Airtable](/integrations/airtable) — Create records in an Airtable base
  - [Notion](/integrations/notion) — Create pages in a Notion database
  - [Slack](/integrations/slack) — Post submissions to Slack channels
  - [Discord](/integrations/discord) — Post submissions to Discord channels
  - [Linear](/integrations/linear) — Create issues from submissions
  - [GitHub](/integrations/github) — Create GitHub issues from submissions
  - [Webhooks](/integrations/webhooks) — Send signed JSON to your endpoint
</div>

<p>
  Zapier and Make also appear in the provider grid, marked <strong>Coming soon</strong>: the cards are visible, but setup is blocked until
  those apps ship. Zapier already has a formbase app you connect from inside Zapier; drive Make with its HTTP module.
</p>

> ℹ️ **Step by step in Zapier**
> <p>
>     The <a href="/guides/overview">Zapier guides</a> connect the formbase app for Zapier and walk through each trigger and action click by
>     click.
>   </p>

<h2 id="plans">Plan availability</h2>

<ul>
  <li>Cal.com and every submission integration are available on every plan.</li>
  <li>
    Sending abandoned submissions to integrations requires Pro or Business. Every submission integration except Webhook supports abandoned
    events.
  </li>
  <li>Google Analytics and Axiom analytics streaming are available on Free, Pro, and Business.</li>
  <li>Axiom respondent-answer streaming is included with analytics streaming, but stays off until enabled on a specific form.</li>
</ul>

> ⚠️ **Review data before sending it elsewhere**
> <p>
>     Integrations can send respondent data to services you control. Configure only destinations you trust, map only fields you need, and make
>     sure your respondent notice and processing agreements cover those transfers. Abandoned submissions are especially sensitive because the
>     respondent has not pressed Submit.
>   </p>

<h2 id="reliability">Delivery and connection health</h2>

<p>
  Submission integrations use a durable delivery queue: up to 5 attempts per submission with exponential backoff, an event log on each
  integration, a failure email, and a <strong>Retry all</strong> button for deliveries that ran out of attempts. OAuth connections are
  refreshed automatically when providers support refresh tokens. See <a href="/integrations/health-monitoring">Integration health</a>.
</p>

<p>
  When a destination supports field mapping or message templates, you can include <strong>PDF Link</strong> to send a link to the generated
  submission PDF with each delivery.
</p>

<p>
  Analytics event forwarding is intentionally different: it is best-effort and has no retry queue. Axiom respondent answers use durable
  delivery because each answer payload represents one submission.
</p>