App integration · All integrations

Route Signed Forms to HubSpot — Without the JotForm Add-On Stack

Getting JotForm, HubSpot, and a signature tool to hand off data cleanly is harder than it looks. You collect the response in JotForm, route it to HubSpot, then trigger a separate signing step — and the countersigned PDF rarely lands on the right contact record automatically. Clinics, agencies, and real-estate teams managing intake and consent workflows stitch these tools together by hand, losing hours every week chasing signed documents across inboxes and deal records.

Formfy combines the form builder, e-signature layer, and webhook delivery in one tool. One API key routes signed consents, waivers, and intake packets directly to HubSpot the moment a client signs — no separate signature app or middleware required.

Start a 15-day free trial Read the OpenAPI spec

The workflow at a glance

Trigger

A client signs a Formfy consent, intake, or waiver form

Action

Formfy fires a form.signed webhook to HubSpot's Private App receiver

Result

HubSpot contact is created or updated and the countersigned PDF is attached to the deal record

Step-by-step: connect HubSpot to Formfy

Set up a Formfy webhook subscription and route signed consents, intakes, and waivers directly into HubSpot contacts and deal records.

  1. Generate a Formfy API key

    Open the Formfy dashboard, go to Settings → API Keys, and click Create key. Copy the fk_live_… token immediately — Formfy shows it once. During development use a fk_test_… key so test submissions don't count against your live plan credits.

  2. Build your intake form from a template

    Call GET /api/v1/templates to browse consent, intake, and waiver starters. Pick one that fits your workflow, then POST /api/v1/forms to create a live instance. Starting from a template saves the fieldwork of writing consent language and signature blocks from scratch.

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

  3. Subscribe HubSpot to the form.signed event

    POST /api/v1/webhooks with your HubSpot receiver URL as target_url and event_types: ["form.signed"]. Formfy returns a signing secret — store it in HubSpot so the workflow step can verify the X-Formfy-Signature header and reject spoofed payloads before processing.

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

  4. Configure the HubSpot workflow to create or update the contact

    In HubSpot, build a workflow triggered by the incoming webhook. Map signer_email, form_id, and signed_at onto contact properties. Add a secondary action to write the signed PDF URL as a note on the contact timeline or attach it directly to the active deal.

  5. Retrieve the signed PDF and verify the end-to-end flow

    Sign a test form in Formfy, then call GET /api/v1/forms/{id}/signed-pdf to confirm the countersigned document is ready. Check HubSpot for the new contact record. If both appear, the pipeline is live — every future signing runs the same route without manual intervention.

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

Subscribe HubSpot to Formfy signed-form events

Subscribe to the form.signed event and point the delivery at your HubSpot Private App receiver URL. Formfy returns a signing secret used to verify every X-Formfy-Signature header before HubSpot processes the payload.

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://your-hubspot-receiver.example.com/hooks/formfy",
    "event_types": ["form.signed"]
  }'

Frequently asked questions

Does Formfy have a native HubSpot app in the marketplace?

Not yet. Today you connect Formfy to HubSpot via webhooks: subscribe to form.signed in Formfy, point the delivery at a HubSpot workflow webhook trigger or a Zapier middleware step, and map the payload fields onto contact properties. A dedicated HubSpot marketplace app is on the roadmap, but the webhook route is fully functional and ships in under 15 minutes.

How does this compare to the JotForm HubSpot integration?

JotForm routes form response data to HubSpot contact fields — useful for lead capture. Formfy adds built-in e-signatures and generates a countersigned PDF in the same step, then ships both the contact data and the signed document to HubSpot in a single webhook payload. Teams replacing the JotForm stack can remove a separate DocuSign or HelloSign subscription.

Which Formfy events can I route to HubSpot?

Five event types are live in v1: form.created, form.sent, form.viewed, form.signed, and form.expired. form.signed is the most actionable for HubSpot workflows — it carries signer_email, form_id, signed_at, and a URL to the countersigned PDF. Subscribe to multiple events in one webhook by listing all of them in the event_types array when you POST /api/v1/webhooks.

Can I attach the signed PDF to a HubSpot deal or contact record?

Yes. After the form.signed webhook fires, call GET /api/v1/forms/{id}/signed-pdf with your Bearer token to retrieve the countersigned document URL. Pass that URL into a HubSpot workflow action to create a note, file attachment, or deal activity. The signed PDF is ready within seconds of the client signing.

Does Formfy support SMS form delivery the way JotForm does?

Yes. POST /api/v1/forms/{id}/send accepts a phone number in the recipient field and delivers the form link via SMS. This is especially useful for clinic intake and field-service consent workflows where clients are on mobile and unlikely to be at a desktop when you need the signature.

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

Formfy queues the webhook delivery and retries with exponential backoff for up to 24 hours. Once HubSpot's receiver recovers, the queued payloads fire automatically. You can also inspect every delivery attempt in the Formfy dashboard's Webhook Deliveries log and replay any failed payload by hand.

Can I trigger a Formfy form send from inside a HubSpot workflow?

Yes. Add a HubSpot workflow action that calls POST /api/v1/forms/{id}/send via an outbound webhook. Pass the enrolled contact email as the recipient and include an optional custom message. The client receives the Formfy form link by email or SMS and the signed result routes back to HubSpot via your form.signed subscription.

Which Formfy plans include API and webhook access?

The Formfy public API and webhook firehose are 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 full HubSpot pipeline before upgrading. Rate limits scale with your plan tier; X-RateLimit-* response headers report your current quotas on every API response.

Ready to wire HubSpot 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