Integrations
Where a response can go once it has been submitted.
An integration is configured per form: open the form, pick a provider, connect it, and every response from then on is sent there.
Available today
| Integration | What it does | Setup |
|---|---|---|
| Google Drive | Files a PDF of each response into a Drive folder | Connect your Google account |
| Zapier | POSTs each response to a Zapier Catch Hook | Paste the hook URL, no account keys |
| Make | POSTs each response to a Make custom webhook | Paste the webhook URL, no account keys |
Zapier and Make are the quickest to try: there is no OAuth step, just a URL you copy from the scenario you are building. Through either of them, a response can reach thousands of other tools.
There is no separate “webhook” card. The Zapier and Make cards are plain JSON POSTs to whatever URL you paste, so either one delivers to an endpoint of your own just as well, and either can carry an optional signing secret, which makes each delivery arrive with an HMAC-SHA256 signature you can verify. See Webhooks.
How delivery works
- Delivery runs as part of the submission, so a response appears at the other end immediately.
- Every attempt is recorded and shown as Recent Activity on the form’s Integrations tab, the 20 most recent attempts for that form.
- A failed delivery is logged and the response is still saved, but it is not retried later: there is no delivery queue and no dead-letter handling. Webhook calls themselves time out after 15 seconds and are attempted twice before being recorded as failed.
- OAuth connections refresh their own access token. If the refresh fails the card is marked Needs attention and you reconnect it.
More providers
Other providers are being worked on and are not documented here until they are switched on in the app. In the meantime, Zapier and Make reach most tools: both POST each response to any URL you give them.
Uploaded files in an integration payload
Where a response includes uploaded files, the payload carries signed links to them rather than the files themselves. Knowing a file’s ID is not enough to read it. The link’s signature is what authorises the read, and where a link lifetime is configured on the deployment, the link stops working after it.
Connection problems
If a connection stops working (a revoked token, a changed password on the provider’s side) reconnect the provider from the form’s integration settings.