Skip to main content
Question

zapier inquiry forms

  • March 31, 2026
  • 2 replies
  • 23 views

Byron Honea
Rising Star
Forum|alt.badge.img

I’m running into an issue with Zapier + HoneyBook and wanted to see if anyone else has dealt with this.

I’m using the “New Inquiry” trigger, but Zapier is only pulling data from our old HoneyBook forms that we’ve already replaced.

The problem:

  • Our new forms are working — leads are coming in correctly
  • The Zap does trigger for new inquiries
  • BUT when I try to map fields, Zapier only shows fields from the original/old form
  • When I click “Find new records”, it only finds submissions tied to the old form
  • So I can’t select or use the new form fields at all

It basically feels like:
👉 Only the original inquiry form is being recognized as a “record structure” on the HoneyBook side
👉 New forms don’t update or refresh the available fields in Zapier

End result:
The automation runs, but I can’t pull the correct data because the fields available in Zapier are outdated.

Has anyone run into this before or found a workaround to get Zapier to recognize new HoneyBook form fields?

2 replies

Monica R
HoneyBook Employee
Forum|alt.badge.img+7
  • HoneyBook Employee
  • April 1, 2026

Hey ​@Byron Honea! Great use case. 

At this time, only the following fields will be sent to Zapier when a new inquiry is created/project booked:

  • project_url:
  • project_name
  • project_id
  • project_date
  • project_time
  • project_end_date
  • project_end_time
  • project_location
  • project_type
  • project_timezone
  • workspace_id
  • company_id
  • company_name

 

I’m hoping we’re able to add some more fields and flexibility to the connection in the near future! Thanks again for surfacing this to the Community.


Byron Honea
Rising Star
Forum|alt.badge.img
  • Author
  • Rising Star
  • April 23, 2026

another response I received to help anyone that has trouble! thanks to the team for investigating my issue so well!

After doing some research with the engineers, we were able to determine that the Zapier integration was specifically designed for contact forms. Lead forms are a bit newer to the product, so the mappable fields from lead forms do not translate in Zapier! With that said, the engineers are looking to change this behavior! I can't promise that the feature will be updated in the future; however, the engineers are looking further into this and how we can change the behavior.

Currently, when you set up the Zap and click "find a sample," HoneyBook only looks at Contact Form data to build the list of fields you can map. It doesn't look at Lead Forms at all. That's why the fields shown in Zapier look like the old contact form.

I hope this explanation helps! Right now, using the older contact form may be a better option, or you can continue to use the lead form; however, the custom fields from your custom forms will not be collected in Zapier.