Gravity Forms logo
HubSpot logo

Workflow template

Save Gravity Forms contacts in HubSpot and verify the result

Connect Gravity Forms and HubSpot, select your form and let FastHook manage the submission feed. Save the contact, read it back by ID and receive a minimal receipt only when the submitted details, entry marker and selected owner match.

How it works

From a Gravity Forms entry to a verified HubSpot contact

1 Trigger · 3 Transformations · 2 Actions
Gravity Forms1 · Trigger

Gravity Forms submission

Use the native Form Submitted trigger for one selected form. FastHook creates and authenticates its official Webhooks Add-On feed; you do not copy a webhook URL or map a feed manually.

FastHook2 · Transformation

Configure Gravity Forms and contact owner

Choose a unique site key, HubSpot owner ID and input IDs for email, first name and last name. Read those values from the native entry, reject inactive or incomplete submissions before CRM writes, and build a site:form:entry marker.

HubSpot3 · Action

Save contact and submission marker

Create or update one contact by email in the connected HubSpot portal. Write the submitted names, configured owner and entry marker. Existing values in these five mapped properties can be overwritten.

FastHook4 · Transformation

Require one completed contact write

Continue only when HubSpot returns one completed, non-archived contact with a valid record ID. An accepted request, incomplete batch or partial error cannot issue a receipt.

HubSpot5 · Action

Read the saved contact by ID

Retrieve the exact record returned by the write, including its email, names, owner and entry marker. This avoids using an eventually indexed CRM search as proof of a save.

FastHook6 · Transformation

Verify fields and issue a minimal receipt

Compare all five properties against this submission and reject mismatches. On success, output only contact_id and saved_at, using HubSpot's record update timestamp.

The result

A record ID and saved timestamp after read-back

Illustrative final step output

{ "contact_id": "123456789", "saved_at": "2026-11-17T12:00:00.000Z" }

Fictional example. The receipt is available in FastHook run output after the CRM read-back; it is not the immediate webhook response or the confirmation shown to the form visitor. Earlier run steps still contain the submitted contact data.

Before activation

Set up your workflow

  1. Prepare Gravity Forms and a test HubSpot portal

    Use self-hosted WordPress with Gravity Forms and its official Webhooks Add-On. The add-on is included with eligible Elite or Nonprofit licenses; check your license before starting. Enable Forms → Settings → REST API and use a dedicated Read/Write Gravity Forms key or a WordPress application password whose user can read forms and manage Webhooks Add-On feeds. In your own HubSpot test portal, create a Contact property of type single-line text with internal name fasthook_gravity_entry_id. Choose a valid contact owner and note their numeric owner ID. The Gravity Forms HubSpot Add-On and FastHook's WordPress.com connection are not required.

  2. Connect both apps and select the form

    Install the template as a draft. Connect the intended Gravity Forms installation and HubSpot portal, then select your form in the Gravity Forms Form Submitted trigger. Confirm the account identities before testing. In Configure Gravity Forms and contact owner, enter a unique site_key such as my-practice-site and the numeric owner_id as a string. This fixed owner does not reproduce another plugin's routing rules.

  3. Set input IDs and let FastHook manage delivery

    Set email_input_id, first_name_input_id and last_name_input_id in the configuration step. Defaults 2, 1.3 and 1.6 illustrate Email field 2 and the First/Last inputs of Name field 1; change them to match your own form. Separate name fields also work. Use Gravity Forms Get Form to inspect fields[].id and fields[].inputs[].id if needed. Form and entry IDs come from the native event automatically. When activated, FastHook creates the authenticated feed for the selected form; no manual webhook URL, request header or feed mapping is needed. Do not manually edit its managed feed. Existing installed copies using a manual webhook are not automatically migrated.

  4. Submit fictional data and inspect the receipt

    Disable competing HubSpot contact feeds for this test form, activate the test workflow and submit one uniquely named fictional contact through the actual form. Direct Create Entry API writes do not fire Form Submitted. Inspect the HubSpot record and FastHook's final receipt. Submit a second entry with the same email to check the update path and marker change. Where the form permits it, test a missing first or last name: no CRM write or receipt should occur. A mismatched CRM read-back must not issue a receipt. Review errors before retrying because a completed write is not rolled back. Pause the test workflow when finished; the integration manages its own feed lifecycle.

Details and limitations
  • Specifically for Gravity Forms. This template uses FastHook's native Gravity Forms Form Submitted trigger and the official Webhooks Add-On. Fluent Forms, Contact Form 7 and embedded HubSpot forms have different APIs and payloads. This is not a generic form-plugin integration or a WordPress.com API connection. The managed trigger forwards the native entry, so earlier run steps can contain additional form fields; keep sensitive data out of your test form.

  • FastHook performs the contact write. This is an alternative delivery flow, not an independent audit of the Gravity Forms HubSpot Add-On. Running both contact feeds may cause competing updates. Do not use this receipt to claim that another plugin, native form analytics or a HubSpot marketing-form submission succeeded.

  • A current matching record is the proof. Verification checks the saved record ID, email, names, fixed owner and site/form/entry marker. A webhook HTTP 200 or an old contact with the same email is insufficient. The timestamp is HubSpot's record updatedAt value, not a promise about form delivery latency. Concurrent CRM updates can cause a mismatch and no receipt even after a successful write.

  • A failed check does not undo a write. API failures and property mismatches stop the workflow without a receipt. There is no additional polling loop for delayed owner assignment. Inspect the saved contact and run before retrying. Retries and out-of-order entries can overwrite newer names, owner and marker; this starter does not guarantee exactly-once delivery or preserve a history of every submission.

  • Contacts do not verify deal pipelines. The flow sets a contact owner but creates no deal, pipeline stage or association. Marketing consent, subscription status, CAPTCHA and spam filtering are separate responsibilities. A form submission blocked before the webhook is not visible to this workflow.

  • Plan for the existing services. You need WordPress hosting, a suitable Gravity Forms license, a HubSpot account with the required contact/property permissions and FastHook usage capacity. Allow for provider rate limits and maintenance when form fields, owner IDs, properties or permissions change. Email receipts, visitor confirmations and failure notifications require additional steps.

Questions about this template

Do I still need to create a webhook feed manually?

No. Connect Gravity Forms, select the form and activate the configured workflow. FastHook creates an authenticated feed through the official Webhooks Add-On and manages its lifecycle. The add-on and a suitable license are still required.

Does this work with every WordPress form plugin?

No. The prepared payload and instructions are for Gravity Forms with its official Webhooks Add-On. Fluent Forms, Contact Form 7 and embedded HubSpot forms require their own mappings and tests.

Do I need Gravity Forms' HubSpot Add-On?

No. FastHook performs the contact upsert and subsequent read-back. Disable any competing CRM feed for the test form. This template cannot independently certify a save performed by another add-on.

Why create a custom contact property?

fasthook_gravity_entry_id stores a site:form:entry marker. Reading that exact marker back helps distinguish the current entry from a previously saved contact with the same email. It is a latest-entry marker, not an immutable submission log.

What is overwritten on an existing contact?

The mapped email, first name, last name, selected owner and entry marker are written by the upsert. Use a test portal first and agree these overwrite rules before sending real enquiries.

Will the visitor immediately see the receipt or receive an email?

No. Gravity Forms' webhook response only acknowledges ingress. The verified receipt appears later in the final FastHook step. Sending it to staff by email or showing an asynchronous status on the website requires additional configuration.

Will my existing installed workflow switch to the native trigger?

No. This updated template creates a new native-trigger draft. Existing installed workflows keep their previous configuration. Configure and test the new draft, then deliberately stop the old delivery flow before using it for real enquiries.

Explore connected apps