Integrations
Connect your workflow
Schedule appointments, stream analytics, deliver submissions, and connect formbase to tools your team already uses.
Three connection models
Integration setup differs by feature. Knowing which model you are using explains where configuration lives and what starts happening after you connect.
| Model | Scope | What happens |
|---|---|---|
| Scheduler connection | Connect Cal.com once per workspace; choose an account and event type on each Schedule appointment question. | Respondents book through a native formbase question. |
| Analytics destination | Connect GA4 or Axiom once per workspace. | Pseudonymous analytics events start forwarding for every form by default; each form can opt out. |
| Submission integration | Connect an account at workspace level, then configure delivery separately for each form. | Completed submissions—and optionally abandoned submissions—are delivered with retries. |
Available connections
Zapier and Make also appear in the provider grid, marked Coming soon: 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.
Step by step in Zapier
The Zapier guides connect the formbase app for Zapier and walk through each trigger and action click by click.
Plan availability
- Cal.com and every submission integration are available on every plan.
Sending abandoned submissions to integrations requires Pro or Business. Every submission integration except Webhook supports abandoned events.
- Google Analytics and Axiom analytics streaming are available on Free, Pro, and Business.
- Axiom respondent-answer streaming is included with analytics streaming, but stays off until enabled on a specific form.
Review data before sending it elsewhere
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.
Delivery and connection health
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 Retry all button for deliveries that ran out of attempts. OAuth connections are refreshed automatically when providers support refresh tokens. See Integration health.
When a destination supports field mapping or message templates, you can include PDF Link to send a link to the generated submission PDF with each delivery.
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.