App integration · All integrations
Connect Formfy to Airtable
Every signed intake form, consent, or waiver that lands in Formfy creates a new data point your team needs — client name, signature timestamp, form type, signed PDF link. Without an automated pipeline, someone copies that information by hand into a spreadsheet or a project tool, then tracks down the PDF file later. Clinics, agencies, and operations teams using Airtable as their source of truth end up with signed forms scattered across email inboxes and dashboards, out of sync with the records that actually drive their work.
Formfy's webhook API fires the moment a form is signed. Route that payload into Airtable through Make, Zapier, or a direct HTTP call, and every signed record — name, email, timestamp, PDF URL — writes itself into your base without manual effort.
The workflow at a glance
Trigger
A client signs a Formfy consent, intake, or waiver form
Action
Formfy fires a form.signed webhook; your automation tool maps fields to Airtable
Result
A new Airtable record appears instantly with signer details, timestamps, and the signed PDF URL
Step-by-step: connect Airtable to Formfy
Wire Formfy webhook subscriptions into Airtable via Make or Zapier and automatically create records every time a form is signed.
Generate a Formfy API key
Open the Formfy dashboard, navigate to Settings → API Keys, and click Create key. Copy the fk_live_… token to a secure location — Formfy shows it once. Use a fk_test_… key while you wire up the Airtable pipeline so test submissions do not consume live credits.
Prepare your Airtable base and table
In Airtable, open the base where you want signed-form records to land. Add columns for the fields Formfy sends: signer_email, signed_at, form_id, form_title, and signed_pdf_url. Matching column names to payload keys makes field mapping faster in Make or Zapier and keeps the base readable when your team opens it.
List existing Formfy webhooks
Before creating a new subscription, verify what Formfy already publishes. Send GET /api/v1/webhooks with your Bearer token. The response array shows every active subscription with its event types and target URLs, so you can confirm no duplicate form.signed hook is already firing.
GET
/api/v1/webhooksSee in the OpenAPI spec →Subscribe to the form.signed event
POST /api/v1/webhooks with your automation tool's receive URL — from Make, a Zapier Catch Hook, or your own endpoint — and set event_types: ["form.signed"]. Formfy returns a webhook ID and a signing secret. Store both: the secret lets you verify X-Formfy-Signature on every delivery.
POST
/api/v1/webhooksSee in the OpenAPI spec →Map Formfy payload fields to Airtable columns
Inside Make or Zapier, add an Airtable Create Record action. Map submission_id to a record ID field, signer_email to Email, signed_at to Date, and form_id to Form ID. For the signed PDF, add a URL field — Formfy includes a signed_pdf_url in the webhook payload ready to store.
Fetch and attach the signed PDF
If you need the signed PDF as an Airtable attachment rather than a URL, call GET /api/v1/forms/{id}/signed-pdf with the form_id from the webhook payload. The response redirects to a time-limited download URL. In Make, use an HTTP module to fetch the file bytes, then pass them to the Airtable Upload Attachment action.
GET
/api/v1/forms/{id}/signed-pdfSee in the OpenAPI spec →Test end-to-end and rotate the webhook secret on schedule
Sign a test form in Formfy and verify the Airtable record appears within 30 seconds. Quarterly, POST /api/v1/webhooks/{id}/rotate-secret to issue a fresh signing secret, then update the value in your automation tool. Deliveries fail closed until both sides agree on the new secret — by design.
POST
/api/v1/webhooks/{id}/rotate-secretSee in the OpenAPI spec →
Subscribe to Formfy signed-form events for Airtable routing
Create a webhook subscription that fires on every form.signed event. Supply the receive URL from Make or Zapier as target_url; Formfy returns a signing secret to verify every delivery.
curl -X POST https://formfy.ai/api/v1/webhooks \
-H "Authorization: Bearer fk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"target_url": "https://hook.eu1.make.com/abc123xyz",
"event_types": ["form.signed"]
}'Frequently asked questions
Does Formfy have a native Airtable integration?
Not a one-click app-store connector today, but the combination works cleanly via Formfy's public webhook API and the free tier of Make or Zapier. You subscribe Formfy to push signed-form events to your automation tool's receive URL, then map payload fields onto an Airtable Create Record step. The full pipeline takes about ten minutes to configure and runs without writing any code.
Which Formfy events can I route into Airtable?
Five event types are available in v1: form.created, form.sent, form.viewed, form.signed, and form.expired. For most Airtable pipelines, form.signed is the right trigger — it fires when the last required signer completes their signature and the document is fully executed. Subscribe to multiple events on a single webhook by listing all of them in the event_types array when you POST /api/v1/webhooks.
How do I attach the signed PDF to an Airtable record?
Call GET /api/v1/forms/{id}/signed-pdf with the form_id from the webhook payload. Formfy returns a redirect to a time-limited signed URL for the completed PDF. In Make, add an HTTP module to download the file binary, then pass it to the Airtable Create Attachment action. The file lands in an Attachment-type field alongside the rest of the signed-form data.
Can I trigger a Formfy form send from an Airtable record?
Yes. Use Make or Zapier to watch for new Airtable records and call POST /api/v1/forms/{id}/send with the recipient email or phone number from the Airtable row. Formfy delivers the form link by email or SMS within seconds. You can also call POST /api/v1/forms to generate a new form instance from a template before sending, passing field defaults from the Airtable record.
How do I verify Formfy webhook signatures before writing to Airtable?
Formfy includes an X-Formfy-Signature header on every delivery, computed as HMAC-SHA256(signing_secret, raw_body). In Make, add a Tools → Crypto module before the Airtable step to recompute the HMAC and compare it to the header value. Only write the Airtable record if the signatures match. The signing secret is returned once on subscription creation and can be refreshed via the rotate-secret endpoint.
What happens to Airtable records if a webhook delivery fails?
Formfy queues the delivery and retries with exponential backoff for up to 24 hours. Once your receive endpoint responds with a 2xx status, Formfy marks the delivery successful and stops retrying. You can inspect every attempt in the Formfy dashboard's Webhook Deliveries log and replay any failed delivery manually — no records are permanently lost, just delayed until the next successful attempt.
Does the Formfy free trial include API and webhook access?
Yes. The 15-day free trial includes access to the public REST API, webhook subscriptions, and signed PDF download endpoints. Generate a fk_test_… key during the trial to build and validate your Airtable pipeline before committing to a paid plan. Rate limits apply and scale with your plan tier — check the X-RateLimit-* response headers for current quotas.
Can I route different Formfy form types to separate Airtable tables?
Yes, and there are two clean approaches. First, create separate webhook subscriptions for each form or form group, each pointing to a different receive URL in Make or Zapier, and route each scenario to its own Airtable table. Second, use a single webhook with a router step that branches on form_id or form_title from the payload before writing to the correct table.
Ready to wire Airtable into Formfy?
Spin up an API key, run your first webhook, and route signed forms wherever your team already works.