HigherStack Integrations overview
How connectors work, how delivery + retries + alerts keep them reliable, and how your tokens are kept safe.
Integrations send each submission somewhere else the moment it arrives — a Notion database, an Airtable base, a Google Sheet, a webhook endpoint, or an advertising platform for conversion tracking. You configure them in a form’s Integrations area.
Two families of integration
| Type | Examples | What they do |
|---|---|---|
| Data destinations | Notion, Airtable, Google Sheets, Webhooks | Create a record / row / HTTP payload from each submission. |
| Conversion tracking | Meta, Google Ads, TikTok, LinkedIn | Report a conversion to an ad platform so you can measure and optimize campaigns. |
Reliable delivery
When a submission comes in, deliveries fire automatically. If a destination is temporarily unavailable, conversions are retried on a backoff schedule (roughly 30 minutes, 2 hours, 8 hours, then 24 hours). Every attempt is logged so you can see what happened in the conversion health view, and persistent failures send you an email alert.
Where alerts go
Failure alerts are emailed to the form’s notification address. If a form has none, they fall back to the workspace alert email — set one in workspace settings so nothing slips through.
How your credentials are protected
API tokens and OAuth connections are stored server-side only and are never sent to the browser or shown again after you save them. The form only knows whether a connection is connected. To change a token, disconnect and reconnect.
Connecting integrations requires edit access (owner or editor). See Roles & permissions.
Still need help?
A dedicated support form is coming soon. In the meantime, jump back into the product or reach the team from the contact page.