Integration setup differs by feature. Knowing which model you are using explains where configuration lives and what starts happening after you connect.
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. >
> 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. >
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.
# Cal.com scheduling Let respondents choose and book a Cal.com appointment without leaving your form. ## Cal.com scheduling Add a native Schedule appointment question, connect Cal.com, and let respondents book an available slot inside the form. > ℹ️ **Available on every plan** >Cal.com scheduling is available on Free, Pro, and Business plans.
Schedule appointment is a formbase question, not an iframe. It uses your form's theme and language, participates in conditional logic, and records confirmed booking details with the submission. Cal.com supplies event types, availability, calendar invitations, and meeting links.
You can also connect accounts from Workspace → Integrations → Scheduling → Cal.com. Connections belong to the workspace, so workspace members can reuse them on other forms and connect additional Cal.com accounts.
If no fields are mapped, respondents enter their name and email in the scheduling question. When fields are mapped, their answers flow into booking details automatically.
> Cal.com confirms the appointment when the respondent clicks Book. The booking then attaches to the form submission when they submit the > form. Until then the appointment exists on the host's calendar even if the respondent walks away. On a public link, formbase releases it > again when the form is still not submitted 24 hours after booking; on a request, when the request is cancelled or expires. It is also > released when you delete the submission or the form. >
If a time is taken by someone else between listing and booking, the respondent is told so and sees the times that are still free. If a booking attempt fails halfway, formbase cancels the calendar entry it created rather than leave the host with a booking the form does not know about, and a second device cannot book the same question twice.
Logic can show or hide Schedule appointment like any other question. Example: ask whether a lead has budget and authority; reveal booking only when both answers qualify.
A visible Schedule appointment question must have a confirmed booking before submission. A hidden one does not block submission. Once a respondent books, the answers that decide whether the question shows are locked, so a later answer cannot hide the booking by accident; to change one, they cancel the booking first. If the question is hidden when the form is submitted anyway, for example because a branching rule skipped its page, that booking is cancelled on Cal.com, so the host's calendar matches the submission.
Publishing is blocked while a Schedule appointment question is missing either half of its setup:
Each message points at the question that caused it. In the editor, the same three states show on the question as{' '} Not connected, Event missing, and Configured badges.
An event type that needs more than a name, an email and a time cannot be booked from a form. Event types that require confirmation, recur, have seats, cost money, or ask required booking questions are listed as Not bookable from a form and cannot be selected; a form that still points at one is blocked from publishing until you choose another event type.
Booking details appear under the Schedule appointment question in the submission table and detail view, with the date and time in your own language. They are also available to notification emails, generated PDFs, CSV/Excel exports, webhooks, and mapped integrations. Webhooks, Zapier, n8n, Make, request callbacks and the API receive the booking as data: start and end time, time zone, attendee, meeting link, Cal.com booking id and status. See Bookings and payments.
formbase keeps listening after submission. When the respondent or the host reschedules or cancels through Cal.com, or the host rejects the booking or marks a no-show, the booking on the submission is updated: its status changes, and the text shown for it starts with{' '} Rescheduled, Cancelled, Rejected, or No-show. The table, exports, the API and regenerated PDFs show the current state. Integrations are not sent again: the submission itself did not change.
Deleting a submission, or the whole form, cancels its appointments on Cal.com so the host does not keep a slot for answers that no longer exist.
> ⚠️ **Edit after submission is disabled** >> Forms containing Payment, Signature, or Schedule appointment questions cannot let respondents edit answers after submission. formbase > turns that setting off during publish so external payment, signature, and booking records cannot drift from submitted answers. >
A daily job refreshes Cal.com OAuth tokens before they expire. A temporary Cal.com outage is retried the next day and changes nothing. If access is revoked, the connection is marked expired: the question shows a Disconnected badge, booking stops working for respondents, and the person who connected the account gets an email naming each published form that books through it. Reconnect Cal.com from Workspace → Integrations → Scheduling, then reselect the account and confirm the event type on each affected question.
Disconnecting a Cal.com account from Workspace → Integrations lists the published forms that schedule appointments through it. Those forms stop accepting bookings, and their owner is emailed. Reconnecting the same Cal.com account restores them: the questions keep the account, so there is nothing to select again.
Toggle Export all form fields to include every question, or turn it off to pick specific fields and set custom column headers.
Column labels default to the question title but can be overridden — helpful when your spreadsheet feeds into another tool that expects specific header names.
Values are written by column position, never by matching the header text. Renaming a header in Google Sheets is harmless; reordering or deleting a column is not, and puts values in the wrong place. When your mapping or your form's questions change, formbase rewrites row 1 of the spreadsheet it created so the header keeps matching what it appends.
A repeating group lets respondents add as many entries as they need — like a list of guests, each with a name and age. In the field picker you choose how to map it:
· , so the Full name
column reads "Jane Appleseed · Marcus Lee".
Pick one, the other, or both. If you remove a member field from your form later, it still appears in the picker so past submissions keep their column — your mapping never breaks.
By default, Submitted at and Submitter are included. Add or remove any metadata column during setup, and rename any of them like a normal column header.
A workspace can have multiple Google accounts connected, and each form picks one. This works well when different teams manage their own Google Drive or you want client spreadsheets in separate accounts.
To add another account, start a new integration setup and authorize with a different Google email. Existing integrations keep their current account.
When you first connect, you can export all existing submissions into the spreadsheet. The backfill runs in the background in batches of 50 rows, with progress shown in the integration panel.
Rows are written in submission order (oldest first) so the spreadsheet reads chronologically.
formbase creates a spreadsheet in your Google Drive when the first submission arrives (not on save). The spreadsheet uses your form's name, or the custom name you set during setup. If you delete the spreadsheet, formbase creates a new one on the next submission — you don't lose any data.
The integration detail panel has a Send test button. It appends a placeholder row to the spreadsheet so you can verify
column mapping without waiting for a real submission. Question columns show
[Question Title] placeholders; metadata columns show synthesized values.
If a respondent starts your form but doesn't finish, formbase can still sync the partial data. On the{' '} Abandoned submissions step, set Send abandoned event after to 12 hours, 1 day, 3 days, or 1 week. An hourly sweep then appends a row with whatever the respondent filled in, using the same column mapping. The Submission status column reads "Partial" so you can filter incomplete responses.
Only drafts from a share link are swept, and Required fields narrows it further: the row is appended only when at least one of the fields you pick was filled in.
> ℹ️ **Pro feature** >> Abandoned response delivery requires a Pro or Business plan. The core Google Sheets integration is available on all plans. See{' '} > plans & pricing. >
After 5 consecutive failures of any kind, the integration auto-pauses with an error status and the person who set it up receives a notification email. Fix the underlying issue and re-enable the integration — it will resume from the next new submission.
No. formbase creates one in your Google Drive when the first submission arrives.
formbase creates a new one on the next submission with the same column headers. No data is lost.
Yes. Google accounts are connected at the workspace level. Any member can use any connected account when setting up an integration — no re-authorization needed.
Yes. Authorize additional accounts during new integration setups. Each form picks which account to use.
Permission to create and edit spreadsheets (Google Sheets API), create files in Google Drive (files only), and read your email and profile name. formbase cannot read your other Drive files or access anything outside the spreadsheets it creates.
Both appear as rows in the same spreadsheet. The "Submission status" metadata column shows "Completed" or "Partial", so you can filter or sort by it.
Yes. Open the integration and re-map fields. The next delivery rewrites the header row to match; existing rows keep the values they were written with.
No. The spreadsheet is fixed once the integration is created. Delete it and create a new one.
Go to Form settings → Integrations → Google Sheets and delete the integration. To also revoke formbase's access to your Google account, visit your Google account permissions page.
The Finalize step and the integration detail panel both have a Send test button that creates a real page in your
database. Text and title properties get [Question Title] placeholders, numbers get
0, emails get test@example.com, dates get the current timestamp, selects use the first available option, and
files get a tiny placeholder image. Delete the test page after verifying.
After connecting, you can backfill past responses into the database. Pages are created one at a time (~3 per second to stay within Notion's rate limits), with progress logged every 10 pages.
Channel reads "Public link" or "Request", and Request ID holds the id of the request a response answered, so a database that collects both share-link and request responses can tell them apart and join back to the request.
If your form has a repeating group, the field picker gives you two ways to map it, depending on whether you want the whole group in one property or each member field broken out.
Member fields that no longer exist in the form but appear in past submissions stay mappable, so syncing never breaks for older responses.
Beyond property mapping, you can compose a rich page body with the template editor. Type @ to insert any form field value or metadata such as PDF Link — the editor shows them as mention chips that resolve at sync time.
Page bodies support paragraphs, bold, italic, underline, and links. Headings, lists, and images are not supported — they render as plain paragraphs. Text is automatically chunked at 2,000 characters per rich-text block (Notion's limit).
If a respondent starts your form but doesn't finish, formbase can still sync the partial data. On the{' '} Abandoned submissions step, set Send abandoned event after to 12 hours, 1 day, 3 days, or 1 week. An hourly sweep then creates a page with whatever the respondent filled in, using the same property mapping as a completed submission. Map the "Submission status" metadata field to a Status or Select property to tell them apart in Notion.
Only drafts from a share link are swept, and you can narrow it further with Required fields — the page is created only when at least one of the fields you pick was filled in.
> ℹ️ **Pro feature** >> Abandoned response delivery requires a Pro or Business plan. The core Notion integration is available on all plans. See{' '} > plans & pricing. >
If you rename a property in Notion, formbase detects the change on the next submission and updates its mapping automatically. Properties are matched by their stable internal ID, so renames are transparent.
If you delete a property, formbase drops it from the mapping and keeps syncing the remaining fields. If a property's type changes to something incompatible (e.g., number becomes select), the value may fail to sync — re-open the integration and re-map that field.
No. Create the database in Notion first, then share it with formbase during authorization.
The next submission fails with a "not found" error and the integration stops. The database is fixed when the integration is created, so delete this integration and create a new one against the new database.
Yes. Notion accounts are connected at the workspace level. Any member can use any connected account when setting up an integration.
Yes. Authorize additional Notion workspaces during new integration setups. Each form picks which account to use.
No. But if you remove formbase from Notion Settings → Connections, the token is revoked and you'll need to reconnect.
Both appear as pages in the same database. The "Submission status" property reads "Completed", "Partial", or "Updated" when a respondent edited an earlier answer — use Notion's filtered views to separate them.
Go to Form settings → Integrations → Notion and delete the integration. To also revoke formbase's access to your Notion workspace, go to Notion Settings → Connections and remove formbase.
@here, @channel, @everyone)
The template editor lets you compose the exact message posted to Slack. Type @ to open the mention menu and pick from:
@here, @channel, and @everyone
Bold, italic, strikethrough, inline code, and links carry through as Slack mrkdwn. Underline does not — mrkdwn has no underline. The message limit is 3,000 characters; a longer message is truncated with an ellipsis.
When a respondent starts your form but doesn't finish, formbase can post a separate message. Set{' '} Send abandoned event after to 12 hours, 1 day, 3 days, or 1 week, and compose a dedicated{' '} Abandoned message — it cannot be left empty. Optionally narrow it with Required fields: the message fires only when at least one of the fields you pick was filled in.
A sweep runs every hour, so a message arrives at the first sweep after the idle window passes, not on the minute. Only drafts from a share link are swept — a request recipient who goes quiet is chased by the request's own reminders instead.
> ℹ️ **Pro feature** >> Abandoned response delivery requires a Pro or Business plan. The core Slack integration is available on all plans. See{' '} > plans & pricing. >
Yes, but you need to invite the formbase bot to the channel first. In Slack, open the private channel and run
/invite @formbase. Then refresh the channel list in formbase — the private channel will appear.
Yes. Each integration has its own channel and message template — for example, one channel for completed submissions and another for abandoned responses.
Yes. Each OAuth install creates a separate connection. Start a new integration and authorize with a different workspace.
Yes. Slack connections are workspace-scoped, not per-user. Any workspace member can use any connected Slack account when setting up an integration.
No. Slack is a notification-style integration — only new submissions are posted after the integration is active. For historical data, use Google Sheets or Notion.
Post messages, post to public channels without membership, read channel lists, read user and group lists (for mentions), and read team info. It does not request admin permissions, message history, or file access.
Go to Form settings → Integrations → Slack and delete the integration. To also remove the formbase bot from your Slack workspace, go to Slack's app management page and uninstall it.
The Discord integration posts submissions to a channel as soon as they arrive. Compose the message with inline mentions of form fields, Discord users, and roles.
formbase connects via OAuth as a bot — no webhook URLs to copy, no IDs to paste. Once the bot is in your server, you can pick any text or announcement channel it has access to.
> ℹ️ **Notifications, not archive** >> Only new submissions are posted after the integration is active. For historical data, use{' '} > Google Sheets or Notion. >
@everyone and @here are not supported (see FAQ).
@everyone and @here are not supported
formbase requests only the permissions needed to deliver messages.
The bot needs:
The bot does not request:
Restrict the bot to a single channel by adjusting Discord's channel permission overrides for the formbase bot role.
When a respondent starts your form but doesn't finish, formbase can post a separate message. Set{' '} Send abandoned event after to 12 hours, 1 day, 3 days, or 1 week and compose a dedicated{' '} Abandoned message — it cannot be left empty. Required fields narrows it further: the message fires only when at least one of the fields you pick was filled in.
A sweep runs every hour, so the message arrives at the first sweep after the idle window passes. Only drafts from a share link are swept — a request recipient who goes quiet is chased by the request's own reminders instead.
> ℹ️ **Pro feature** >> Abandoned response delivery requires a Pro or Business plan. The core Discord integration is available on all plans. See{' '} > plans & pricing. >
Click Invite bot during setup. Pick the target server, confirm permissions, then return to formbase and refresh the server list.
Common causes:
When the integration enters an error state, the person who set it up receives a notification email. Reconnect or delete and recreate the integration. The event log in the detail sheet shows the specific error.
No. formbase does not request the "Mention Everyone" permission, and implicit mentions are disabled at the API level. Use a role mention for broad notifications instead.
The server and channel are fixed after creation. Delete the integration and create a new one pointing to the new channel.
Yes. Each integration targets one server and one channel. To post to multiple servers, create multiple Discord integrations on the same form.
Yes. Discord connections are workspace-scoped. Any workspace member can use any connected Discord account when setting up an integration.
No. Only new submissions are posted after the integration is active. For historical data, use{' '} Google Sheets or Notion.
Go to Form settings → Integrations → Discord and delete the integration. To also remove the bot from your Discord server, go to Server Settings → Integrations in Discord and remove formbase.
Yes, after about 7 days. formbase refreshes them right before each delivery rather than on the daily schedule other providers use. If the refresh fails — the connection was revoked, or the bot was removed — the connection is marked expired and every integration using it stops with an error. Press Reconnect to restore them all at once.
On every submission, formbase POSTs a JSON body to your webhook URL. The request is signed with HMAC-SHA256, retried on failure, and logged in the integration's event log. This page covers setup. The exact payload, headers, and signature algorithm live in the{' '} webhook reference.
You can attach multiple webhooks to a single form. Each fires independently for every event.
https:// everywhere, or http:// for localhost and *.localhost during development.
A refused URL is a configuration problem, not a transient one: the delivery fails permanently instead of retrying.
Every request is the same event envelope — id, type, createdAt, apiVersion,{' '}
test and data. Inside data sit the form, the submission (id, respondent email, submitted time, PDF
link, language), an answers object keyed by field key, and a display object
with the same keys as readable text. Each answer appears once, in each map.
See the reference for the full payload shape,{' '} answers and display, and how a{' '} repeating group is represented.
To preview the exact body for your form, open the integration and expand Example payload under the signing secret. It renders your current mapping with sample answers.
Each request includes an X-formbase-Signature header: t=TIMESTAMP,sha256=HEX, an HMAC-SHA256 of{' '}
TIMESTAMP.BODY computed with your signing secret. The secret itself is never sent. The reference has a{' '}
copy-pasteable verification snippet.
> Without verification, anyone who discovers your URL can post fake submissions. Reject requests where the signature is missing or > invalid. >
Custom webhooks fire only for completed submissions and edits — never for abandoned drafts. A custom webhook is the one receiver that gets both: a Zapier, Make or n8n subscription picks first submissions or edits, never both. For abandoned drafts, use a provider that has an{' '} Abandoned submissions step: Google Sheets, Airtable, Notion, Slack, Discord, Linear, or GitHub Issues. Each takes its own idle window and, where it applies, its own message template. That step requires Pro or Business.
2xx.
Retry-After header on a 429 or{' '}
5xx is honored when it asks for a longer wait.
429, 5xx, timeouts, and connection failures are retried. Every other 4xx fails immediately.
401, 403, and 404 stop the integration right away with an error status and the same email — there
is no waiting for five failures.
Send a test event appears on the Finalize step and again on the saved integration. It POSTs a synthesized example
submission — "John Doe" for text, 42 for numbers, john@example.com for email — signed and with your
custom headers, exactly like a real delivery. From the saved integration it also writes a connection-test entry to the event log.
For local development, expose your dev server with a tunnel:
``` # ngrok ngrok http 3000 # cloudflare tunnel cloudflared tunnel --url http://localhost:3000 ```Yes. Each has its own URL, signing secret, and custom headers. All active webhooks fire independently for every submission.
Yes — up to 5, added during setup or later from the integration. Content-Type is set automatically and any attempt to
override it is ignored.
No. The signing secret is generated once when the webhook is created and cannot be changed. If you need a new secret, delete the webhook and create a new one.
Custom webhooks (configured in Form settings) fire only for completed submissions and updates. For abandoned-draft events, use Slack,
Discord, or a project-management integration — each has a dedicated abandoned-event tab. If you need abandoned events via HTTP, create a{' '}
submission_abandoned subscription through the{' '}
REST API webhook subscriptions, from Zapier, Make, or any other
caller.
Only for localhost and *.localhost during development. All other URLs must use HTTPS.
Delete it from Form settings → Integrations. formbase stops sending requests immediately, and the integration's event history is deleted with it.
formbase auto-creates select options when the submitted value doesn't match an existing option.
Formula, rollup, count, lookup, linked record, collaborator, created/modified time, created/modified by, auto-number, button, and synced-source columns are read-only and cannot be mapped.
A repeating group lets respondents add as many entries as they need — like a list of guests, each with a name and age. In the field picker you choose how to map it:
· , so the Full name field
reads "Jane Appleseed · Marcus Lee".
Pick one, the other, or both. If you remove a member field from your form later, it still appears in the picker so past records keep their field — your mapping never breaks.
If your table has a Rich text, Long text, or Single line text column, you can compose its content with the template editor. Type{' '} @ to insert any form field value or metadata such as PDF Link — the editor shows them as mention chips that resolve at sync time. Rich text columns preserve formatting; other column types receive plain Markdown.
Supported formatting: headings (H1-H4), bold, italic, ~~strikethrough~~, inline code, links, and
ordered/unordered lists. Images and embeds are not supported.
After connecting, you can backfill past responses. Records are written in batches of 10 with a short delay between batches to stay within Airtable's rate limits. Progress is shown in the integration panel.
The Finalize step and the integration detail panel both have a Send test button that writes a placeholder record. Text
columns get [Question Title] strings, numbers get 0, emails get test@example.com, dates get the
current timestamp, and selects use the first option from the question's choices (to avoid creating stray options). Delete the test record
after verifying.
If a respondent starts your form but doesn't finish, formbase can still sync the partial data. On the{' '} Abandoned submissions step, set Send abandoned event after to 12 hours, 1 day, 3 days, or 1 week. An hourly sweep then writes a record using the same field mapping as a completed submission. Map the "Submission status" metadata field to a single-select or text column to tell "Partial" records from "Completed" and "Updated" ones.
Only drafts from a share link are swept, and Required fields narrows it further: the record is written only when at least one of the fields you pick was filled in.
> ℹ️ **Pro feature** >> Abandoned response delivery requires a Pro or Business plan. The core Airtable integration is available on all plans. See{' '} > plans & pricing. >
If you rename a column in Airtable, formbase detects the change on the next submission and updates its mapping automatically. Columns are matched by their stable internal ID, so renames are transparent.
If you delete a column, formbase drops it from the mapping and keeps syncing the remaining fields. If a column's type changes to something incompatible, the value fails to sync — re-open the integration and re-map that field.
Four Airtable scopes: read/write record data, read base schemas, and read your email (to identify the account). Uses OAuth with PKCE — no API keys to manage.
Yes. Airtable connections are workspace-scoped. Any member can use any connected account when setting up an integration.
Yes. Authorize additional accounts during new integration setups. Each form picks which account to use.
The next submission fails with a "not found" error and the integration stops. The base and table are fixed when the integration is created, so delete this integration and create a new one against the new table.
No. These are read-only in Airtable's API. See the full list of excluded column types in the column types{' '} section.
Go to Form settings → Integrations → Airtable and delete the integration. To also revoke formbase's access, go to your Airtable account settings and remove the formbase OAuth app.
[Test]-prefixed issue so you can verify before going live
When you first connect, you can export existing submissions as Linear issues. The backfill runs in the background at ~1 issue per second to stay within Linear's rate limits. Progress is logged every 10 submissions.
When a respondent starts your form but doesn't finish, formbase can create a separate issue for the partial data. Set{' '}
Send abandoned event after to 12 hours, 1 day, 3 days, or 1 week, then fill in the abandoned issue title and description
— neither can be empty. Abandoned issues get a partial-submission label.
An hourly sweep looks for idle drafts, so the issue appears at the first sweep after the window passes. Only drafts from a share link are swept, and Required fields narrows it further: the issue is created only when at least one of the fields you pick was filled in.
> ℹ️ **Pro feature** >> Abandoned response delivery requires a Pro or Business plan. The core Linear integration is available on all plans. See{' '} > plans & pricing. >
Linear access tokens refresh automatically before each dispatch when close to expiry. If refresh fails (token revoked, app uninstalled), formbase marks the integration as error and you receive a failure notification email. Reconnect from the workspace Integrations page to restore.
New submission to <form name>
Three Linear OAuth scopes: read (list teams, projects, and labels),
write (update issue metadata), and issues:create (create issues). The connection uses actor=user,
so issues are attributed to you, not a bot.
Yes. Open the integration detail sheet and change either field. Switching teams resets the project since projects are team-specific.
Yes. Authorize different Linear accounts to add multiple credentials. Each form integration picks which one to use.
Yes. Linear connections are workspace-scoped. Any workspace member can use any connected Linear account when setting up an integration.
The integration auto-pauses and an email goes to the person who set it up. A revoked token, a lost permission, or a deleted team does not wait for five failures — it stops the integration immediately. Either way, fix the cause and press Resume.
[Test]-prefixed issue so you can verify before going live
When a respondent starts your form but doesn't finish, formbase can create a separate issue for the partial data. Set{' '}
Send abandoned event after to 12 hours, 1 day, 3 days, or 1 week, then fill in the abandoned issue title and body —
neither can be empty. Abandoned issues get a partial-submission label, created on first use.
An hourly sweep looks for idle drafts, so the issue appears at the first sweep after the window passes. Only drafts from a share link are swept, and Required fields narrows it further: the issue is created only when at least one of the fields you pick was filled in.
> ℹ️ **Pro feature** >> Abandoned response delivery requires a Pro or Business plan. The core GitHub Issues integration is available on all plans. See{' '} > plans & pricing. >
GitHub OAuth App tokens do not expire — there is no refresh-token rotation. If you revoke the grant from your GitHub account's authorized OAuth Apps page, the next dispatch fails, formbase marks the credential as expired, and you receive a failure notification email. Reconnect from the workspace Integrations page to restore.
New submission to <form name>
@username, GitHub notifies that user, and{' '}
#123 creates an issue reference
Three GitHub scopes: repo (create issues), read:user (identify your account), and read:org (list
organization repos). This is a standard OAuth App — no GitHub App installation required.
Yes. GitHub connections are workspace-scoped. Any workspace member can use any connected GitHub account when setting up an integration.
Yes. Open the integration detail sheet and change either field. Switching repositories resets the milestone since milestones are repo-specific.
The next submission fails with a "not found" error and the integration shows an error status. Edit the integration to pick a different repository.
The integration auto-pauses and an email goes to the person who set it up. A revoked token, a lost permission, or a deleted repository does not wait for five failures — it stops the integration immediately. Either way, fix the cause and press Resume.
> Connecting Axiom starts answer-free analytics events only. Full submissions stay off until you explicitly enable{' '} > Send respondent answers on a specific form. Google Analytics never receives answers. >
Three fixed event names are forwarded:
Every event carries form_id, form_name, and source — link for a public{' '}
share link, request for a request — so a
dashboard can tell the two apart. When available it also carries country, device, browser, traffic source, UTM source, medium and
campaign, referrer host, and, on form_submit, completion duration. Alongside them goes a pseudonymous visitor ID. Events
never contain answer values, respondent email, or question content.
Go to Workspace → Integrations → Analytics, then connect Google Analytics or Axiom. A destination belongs to the whole workspace. Event forwarding starts immediately for every form in that workspace.
Open Form settings → Integrations → Analytics streaming. Each destination provides:
Event forwarding is best-effort. Each destination request is given 3 seconds, failures are swallowed so they never block a respondent, and a failed event is not retried. Analytics are statistical; avoiding one queue row per form view keeps the cost bounded.
Axiom answer streaming rides the submission delivery queue instead: 5 attempts with exponential backoff. After 20 consecutive answer failures, that destination stops being queued until a delivery succeeds or you save a new API token.
Analytics events are pseudonymous, not anonymous. They carry a random visitor ID and coarse traffic/device metadata but no answers. You remain responsible for telling respondents about your third-party analytics, collecting consent where required, and configuring retention in GA4 or Axiom.
Axiom answer streaming can contain personal or sensitive data. Enable it only for datasets you control and only when your privacy notice, lawful basis, and processing agreements cover that transfer.
# Google Analytics (GA4) Forward form views, engagement, and submissions to your Google Analytics 4 property. > ℹ️ **Available on the Free plan.** ## Google Analytics (GA4) Send form_view, form_engaged, and form_submit events to your own GA4 property through Measurement Protocol.G-XXXXXXXXXX
Every event carries form_id, form_name, and source (link or request).
Depending on what is known about the visit, an event can also include:
country, device, and browser
traffic_source, traffic_source_name, traffic_medium, and traffic_campaign
referrer_host
duration_seconds on submit, when available
formbase maps its pseudonymous visitor ID to GA4 client_id. When no ID is available, it sends unknown. Events
never contain answers or respondent email.
form_id, device, or traffic_source as custom dimensions.
form_submit as a key event if submission completion is a conversion for your business.
> Google Measurement Protocol policies prohibit personally identifiable information. formbase never offers answer streaming for GA4. Use > Axiom when you need an opt-in full-submission destination. >
The two region choices are US East 1 (AWS) and EU Central 1 (AWS). Pick the one your Axiom organization lives in — formbase derives the ingest endpoint from it, and ingesting into the wrong region is rejected.
Connecting Axiom turns answer-free event forwarding on for every form in the workspace. Records use event names form_view,
form_engaged, and form_submit, with the same parameters documented in{' '}
Analytics streaming.
{`['your-dataset']
| where ['event'] in ('form_view', 'form_engaged', 'form_submit')
| summarize events=count() by ['event']`}
Each record flattens the event parameters to top level, so form_id, source, device and the rest are
ordinary columns you can filter and summarize on.
Event forwarding is best-effort and not retried. Disable it for one form under{' '} Form settings → Integrations → Analytics streaming → Forward analytics events.
Axiom can also receive one full record per completed submission. This stream is off by default and must be enabled separately for each form with Send respondent answers.
An answer record is the same event envelope a custom webhook receives, plus an Axiom{' '}
_time field: the event id, type, createdAt, apiVersion and test, and under{' '}
data the form, the submission (id, respondent email, submitted time, PDF link, language), an answers object
keyed by field key and a display object with the same keys as readable text. Submissions
that answered a request also carry a request block with your external id and metadata. The full shape is in the{' '}
webhook reference.
Answers are streamed when a submission is completed and again when a respondent edits it. Abandoned drafts never reach Axiom this way — answer streaming has no idle window.
> ⚠️ **Answer records contain personal data** >> A full submission can contain names, emails, free text, files, signatures, and other sensitive answers. Use a restricted dataset, keep > token scope narrow, and set retention/access rules before enabling this stream. >
Answer records ride the submission delivery queue: up to 5 attempts with exponential backoff. After 20 consecutive failures the destination stops being queued, so a bad token or a rejected dataset cannot generate a failing delivery for every new submission. Saving a new API token clears the error and resumes delivery.
Event forwarding and answer streaming have independent switches. You can send answers without events, events without answers, both, or neither for each form.
A daily background job checks the OAuth connections in your workspace, including Cal.com. If a token expires within the next 24 hours, formbase refreshes it automatically — no action needed from you.
This applies to Google, Slack, Linear, Airtable, and Cal.com. Notion and GitHub issue tokens that don't expire, so they're skipped. Discord tokens expire after about 7 days and are refreshed on demand right before each delivery rather than by the daily job.
If a refresh fails — for example because the connection was revoked on the provider side — formbase marks the connection as expired and moves every integration that shares it into an error state. You'll see a warning on each affected integration and receive a notification email.
Each integration card carries a status badge, and opening the integration shows a banner explaining what to do. The badge says{' '} Active, Paused, or Delivery error; the banner is more specific.
Connection problems always take priority. If a token expired, reconnecting fixes every integration that shares that account at once — no need to address each one separately.
When something goes wrong, formbase shows it in two places:
If an integration fails 5 times in a row, formbase pauses it so a broken destination cannot keep burning deliveries. An authentication, permission, or not-found error skips the counter and stops the integration immediately, because retrying cannot fix it.
Either way, an email goes to the person who set the integration up — or to the workspace owner when that address is unavailable. It is sent at most once per integration per 24 hours, so one broken destination cannot flood your inbox.
Fix the underlying issue, then press Resume. Delivery picks up from the next new submission.
Each integration lists its last 20 events under Recent events — deliveries, connection tests, and backfill exports, each marked as passed or failed. A failed entry shows the destination's own error message, so a Notion validation error reads exactly as Notion worded it. A failed backfill also gets a Retry button that restarts the export.
Every delivery gets up to 5 attempts, waiting at least 1, 2, 4, and 8 minutes between them, or longer when the destination asks for more
time through a Retry-After header. formbase looks for due retries every 30 minutes, so each retry can come up to half an hour
later, and the last attempt about two hours after the first.
Submissions that use up all 5 attempts are counted in a banner at the top of the integration: "3 submissions failed to deliver".{' '} Retry all re-queues every one of them and reactivates the integration if it was paused or errored. The banner is hidden when nothing has failed.
> ℹ️ **Analytics destinations are separate** >> Everything on this page covers submission integrations. Analytics event forwarding is best-effort and never retried, and Axiom answer > streaming stops on its own after 20 consecutive failures. See Analytics streaming. >
When a connection expires, click Reconnect on the integration card or in the detail panel. This re-runs the OAuth flow with the same provider. Once authorized, the credential is restored and all integrations using that account resume automatically.
You can also switch to a different connected account from the detail panel if the original account is no longer available.
Once a day. Tokens expiring within 24 hours are refreshed automatically. If you suspect an issue sooner, open the integration detail panel — the health state updates in real time based on delivery results.
No. Submissions are always saved in formbase regardless of integration status. Failed deliveries are queued and can be retried from the detail panel once the issue is resolved.
formbase refreshes tokens proactively, so in most cases you won't notice. If the refresh fails, you receive an email notification immediately — typically before the token actually expires.
The integration switches to the new account. Make sure the new account has access to the same destination (spreadsheet, database, channel). If the destination doesn't exist in the new account, you'll need to update the integration settings.