Automation platform · All integrations

Connect Pabbly Connect to Formfy

Manual handoffs after a client signs a form are one of the quietest revenue drains in any service business. You pull the PDF, paste the email into a spreadsheet, update the CRM, and ping the team on Slack — four steps for every single signature. Multiply that across a week of bookings for a clinic, agency, or studio and the admin overhead compounds fast. What teams actually need is for signed consents and intake forms to flow into every downstream tool the moment the signature lands, without anyone touching a keyboard.

Formfy's public REST API and webhook events connect directly to Pabbly Connect via a catch URL. Subscribe once to form.signed, map the payload onto any of 1,000+ Pabbly apps, and every future signature triggers your workflow — no code, no per-task fees.

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

Pabbly Connect receives the webhook and runs your connected workflow

Result

Submission data lands in Google Sheets, HubSpot, Slack, or any Pabbly-supported app instantly

Step-by-step: connect Pabbly Connect to Formfy

Wire Formfy webhook subscriptions into Pabbly Connect and trigger your first automated workflow from a signed-form event.

  1. Generate a Formfy API key

    Open the Formfy dashboard, go to Settings → API Keys, and click Create key. Save the fk_live_… token somewhere secure — Formfy shows it only once. Use the fk_test_… key during Pabbly workflow development to avoid consuming live submission credits while you build and validate your automation.

  2. List your existing Formfy webhooks

    Before registering a new subscription, confirm what Formfy already delivers. Send GET /api/v1/webhooks with your Bearer token. The response lists every active endpoint and its event types so you can avoid duplicate form.signed deliveries if a subscription is already registered for your destination.

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

  3. Create a Pabbly catch URL and subscribe Formfy to it

    In Pabbly Connect, start a new workflow and choose Webhook as the trigger app. Copy the catch URL Pabbly generates. Then POST /api/v1/webhooks in Formfy with that URL as target_url and event_types: ["form.signed"]. Store the signing secret Formfy returns — you will use it to verify every delivery.

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

  4. Send a test form to capture the sample payload

    Sign a test form in Formfy. Within seconds Pabbly receives the webhook payload containing submission_id, signer_email, signed_at, and form metadata. Click Capture Response in Pabbly to lock in this sample data — all downstream field-mapping action steps depend on it being present.

  5. Add action steps and map the Formfy fields

    Add an action app in Pabbly — Google Sheets Add Row, HubSpot Create Contact, and Slack Send Message are common first choices. Map the Formfy fields captured in the previous step. If the workflow needs the signed PDF as an attachment, call GET /api/v1/forms/{id}/signed-pdf and pass the download URL into the action.

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

  6. Test the complete workflow end-to-end

    Sign another test form and watch the Pabbly task history. Confirm each action step completed with a 200 response and that the destination app reflects the new row, contact, or message. Enable the workflow once the test passes — every future signed form runs the same steps without manual intervention.

  7. Rotate the webhook secret on a quarterly schedule

    POST /api/v1/webhooks/{id}/rotate-secret to issue a fresh HMAC signing key. Update the secret in any Pabbly Code step that verifies the X-Formfy-Signature header. Formfy closes deliveries until both sides agree on the new secret — rotate during a low-traffic window to minimize queued retries.

    POST/api/v1/webhooks/{id}/rotate-secretSee in the OpenAPI spec →

Subscribe Pabbly Connect to Formfy signed-form webhooks

Register your Pabbly catch URL as a Formfy webhook subscriber. Formfy returns a signing secret used to authenticate every payload delivery via the X-Formfy-Signature header.

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://connect.pabbly.com/workflow/receivewebhook/your-catch-id",
    "event_types": ["form.signed"]
  }'

Frequently asked questions

Do I need a native Formfy app in Pabbly to connect?

No. Pabbly Connect treats Webhook as a first-class trigger — no marketplace listing required. You register your Pabbly catch URL as a Formfy webhook subscriber via the public API and the integration works end-to-end today. A dedicated Formfy app in the Pabbly app library may follow in the future, but the webhook path is fully production-ready without it.

Which Formfy events can trigger a Pabbly workflow?

Five event types are live in Formfy v1: form.created, form.sent, form.viewed, form.signed, and form.expired. form.signed is the most useful trigger for clinic intake, agency lead handoff, and real estate workflows. Subscribe to multiple events on a single Pabbly endpoint by listing all of them in the event_types array when you POST /api/v1/webhooks.

How does Pabbly Connect pricing work for Formfy automations?

Pabbly Connect runs on a flat subscription model with unlimited workflow executions — you are not billed per task the way some automation platforms charge. For teams running high-volume consent or intake workflows with dozens of signatures per day, this model keeps automation costs predictable regardless of volume. Check the current Pabbly Connect pricing page for plan details.

How do I send a Formfy form from inside a Pabbly workflow?

Use Pabbly's HTTP Request action step. Call POST /api/v1/forms/{id}/send with your Bearer token, the recipient email or phone number, and an optional custom message. The recipient receives the form link by email or SMS within seconds. You can also call POST /api/v1/forms first to create a fresh form instance from a saved template before sending it.

Can I verify the Formfy webhook signature in a Pabbly Code step?

Yes. Every Formfy delivery includes an X-Formfy-Signature header containing an HMAC-SHA256 hash of the raw body, signed with your webhook secret. Add a Pabbly Code step at the start of your workflow to recompute the HMAC and compare it against the header. Reject the payload if the values do not match — this prevents spoofed or replayed requests from triggering your downstream actions.

What happens if Pabbly is unavailable when a form is signed?

Formfy queues the webhook delivery and retries with exponential backoff for up to 24 hours. Once Pabbly recovers, the queued payloads fire in order. Every delivery attempt — successful or failed — is visible in the Formfy dashboard's Webhook Deliveries log, and you can replay any individual delivery manually so no signed form data is lost during an outage.

Does the Formfy free trial include API access for Pabbly testing?

Yes. The 15-day Formfy free trial includes full API access so you can build and validate your Pabbly workflow before choosing a plan. Use the fk_test_… API key during the trial to avoid billing live submission credits. Rate limits apply and are reported in X-RateLimit-* response headers on every API call; they scale upward with paid plan tiers.

How do I troubleshoot a Pabbly workflow that stopped firing on new signatures?

Run three checks: (1) GET /api/v1/webhooks to confirm the subscription still exists and event_types includes form.signed; (2) open the Webhook Deliveries log in Formfy to see whether Pabbly returned non-200 HTTP responses; (3) if you rotated your API key, note that the webhook subscription authenticates via the signing secret, not the API key — the subscription stays valid after any key rotation.

Ready to wire Pabbly Connect 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