Automation platform · All integrations

Connect Zapier to Formfy

Most form tools force you to copy submissions into your CRM by hand, watch an inbox for signed PDFs, or paste data into Google Sheets one row at a time. Multiply that by every appointment, every client, every consent form — and the busywork eats whole afternoons. Teams want signed forms to flow straight into HubSpot, Slack, Google Drive, and the rest of their stack the moment a client hits submit, without a developer on standby.

Formfy ships a clean public REST API plus a webhook firehose that maps cleanly onto Zapier triggers and actions. You connect Formfy once, then route signed forms into any of 8,000+ Zapier apps with no code.

Start a 15-day free trial Read the OpenAPI spec

The workflow at a glance

Trigger

A client signs a Formfy intake or consent form

Action

Zapier fires a webhook subscription and runs your Zap

Result

Submission lands in HubSpot, Slack, Google Drive, or any of 8,000+ connected apps

Step-by-step: connect Zapier to Formfy

Wire Formfy webhook subscriptions into Zapier and run your first Zap on a signed-form trigger.

  1. Generate a Formfy API key

    Open the Formfy dashboard, navigate to Settings → API Keys, and click Create key. Save the fk_live_… token to a password manager — Formfy shows it once. Use the fk_test_… key during Zap development so you do not bill submissions against your live credits.

  2. List your existing webhooks

    Before adding a new subscription, confirm what Formfy already publishes. Hit GET /api/v1/webhooks with your Bearer token. The response array tells you which event types are already wired so you do not double-fire on the form.signed event.

    GET/api/v1/webhooksSee in the OpenAPI spec →

  3. Subscribe Zapier to the form.signed event

    POST /api/v1/webhooks with target_url set to your Zapier catch-hook URL and event_types: ["form.signed"]. Formfy returns a signing secret — paste it into Zapier as a header so your Zap can verify the X-Formfy-Signature on every payload.

    POST/api/v1/webhooksSee in the OpenAPI spec →

  4. Build your trigger step in Zapier

    In Zapier, choose Webhooks by Zapier → Catch Hook and paste the catch URL. Send a test signature from Formfy to populate the sample payload, then map the submission_id, signer_email, and signed_at fields onto the next step.

  5. Add an action — write to HubSpot, Sheets, or Slack

    Pick the destination app in Zapier (HubSpot Create Contact, Google Sheets Add Row, Slack Send Message). Map the Formfy fields you captured in step 4. If you need the signed PDF in the payload, fetch it via GET /api/v1/forms/{id}/signed-pdf inside the Zap.

    GET/api/v1/forms/{id}/signed-pdfSee in the OpenAPI spec →

  6. Test the Zap end-to-end

    Sign a test form in Formfy. Within 30 seconds your Zap fires, the destination app updates, and Zapier shows a successful task. Turn the Zap on, and every future signed form runs the same workflow without you touching it.

  7. Rotate the webhook secret on schedule

    Quarterly (or on suspected exposure), POST /api/v1/webhooks/{id}/rotate-secret to receive a fresh signing secret. Update Zapier with the new value. Webhook 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 Zapier to Formfy signed-form webhooks

Subscribe to the form.signed event. Zapier supplies the target_url from your Catch Hook step; Formfy returns a signing secret used 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://hooks.zapier.com/hooks/catch/12345/abc/",
    "event_types": ["form.signed"]
  }'

Frequently asked questions

Do I need to build a custom Zapier app to connect Formfy?

No. Formfy works with the built-in Webhooks by Zapier app today. You subscribe Zapier to Formfy events via the public API and use Webhooks by Zapier as the trigger source. A dedicated Formfy app in the Zapier marketplace is on the roadmap but not required to ship live automations.

Which Formfy events can trigger a Zap?

Five event types are live in v1: form.created, form.sent, form.viewed, form.signed, and form.expired. form.signed is the most useful trigger for clinic, agency, and CRM workflows. Subscribe to multiple events on the same webhook by passing all of them in the event_types array when you POST /api/v1/webhooks.

How do I send a Formfy form from a Zap?

Use Zapier's Webhooks by Zapier → POST action. Call POST /api/v1/forms/{id}/send with your Bearer token, the recipient email or phone, and an optional custom message. The recipient receives the form link by email or SMS within seconds. Use POST /api/v1/forms to create a brand-new form instance from a template before sending it.

How fast are Formfy webhook deliveries to Zapier?

Webhook payloads are queued for delivery within seconds of the event firing. Formfy retries failed deliveries with exponential backoff, signs every payload with HMAC-SHA256 via the X-Formfy-Signature header, and exposes a deliveries log so you can replay a failed payload from the dashboard if Zapier was down.

Can I verify the webhook signature in Zapier?

Yes. Formfy includes an X-Formfy-Signature header on every delivery, computed as HMAC-SHA256(secret, raw_body). Inside Zapier, use a Code by Zapier step to recompute the HMAC and compare it to the header before processing the payload. The signing secret is returned once when you create the webhook subscription.

Does the free Formfy plan support API access?

Yes. The Formfy public API is available on every paid plan. The 15-day free trial includes API access too — generate a fk_test_… key during the trial to validate your Zaps end-to-end before upgrading. Rate limits scale with your plan tier; see X-RateLimit-* response headers for current quotas.

What happens if Zapier is down when a form is signed?

Formfy queues the webhook delivery and retries with exponential backoff for up to 24 hours. Once Zapier recovers, the queued deliveries fire automatically. You can also inspect every attempt in the Formfy dashboard's Webhook Deliveries log and replay any delivery manually.

How do I troubleshoot a Zap that stopped firing?

Three checks: (1) GET /api/v1/webhooks to confirm the subscription still exists and event_types contain the event you care about; (2) review the Webhook Deliveries log for HTTP errors from Zapier; (3) if you rotated your API key, the subscription itself remains valid — Formfy authenticates the delivery via the signing secret, not the API key.

Ready to wire Zapier into Formfy?

Spin up an API key, run your first webhook, and route signed forms wherever your team already works.

Start a 15-day free trialSee pricing