Using Zapier for Gravity Forms to Honeybook Contact Forms

I’m actually using it the other direction. I have 10 different DJ Event Types, each with a different HoneyBook contact form (basically, the custom questions for each type vary only slightly). The prospective client selects the Event Type, that page loads with the custom Contact Form, they select the Event Type again and complete the form. Then the Zapier Magic happens. It creates a new line on my tracking Google Sheet, creates a new Google Folder (Date-ClientName-Venue), a new Planning Guide (based on the event type selected) and moves it to the newly created Google Folder, creates a mail folder in GMail, and creates a detailed calendar entry in Google Calendar. All of that is triggered by one HoneyBook Inquiry through the Contact Form!

Oh wow @Rick McLean - I love that automation! Very robust 👏

@Peter Szpakowski, if you’re looking to get data into HoneyBook via Zapier, what you can do is to connect your data source (another form or Google ads, for example) to a an action to either: “create contact” or “create project” in HoneyBook.

Create contact will only create a client instance, while Create project with do both: create a client and a project. This way you will see that project in your pipeline and will be able to immediately start working with them.

Let me know if this helps!

Thank you, Marsha! I’m going to try to make that into something I can share. I need to figure out how to take MY information out of it and make it generic. If you know how to do that, spill the tea!!

Hi Peter, Michal from HoneyBook here 👋🏼

Even though it’s been some time since you asked your question, I have a suggested workflow that might help you to achieve what you’re looking for, in case it is still something you’re trying to do.

In Zapier, create a zap that is triggered by a new inquiry in HoneyBook:
 

When the zap is triggered, part of the information that you receive from the inquiry is a field named “Contact Form Id”, which contains a string of numbers and characters:
 

This ID corresponds to a contact form ID in your account, which you can find in the URL when you go in to edit a contact form:
 

So now, all you have to do is map your contact forms name with their IDs from their URL in HoneyBook, set Zapier to keep this information for you when a new inquiry is coming (say in Google Sheets), and visit that data when you want to get some metrics.

Let me know if you find this useful!

Hi Peter, Michal from HoneyBook here 👋🏼

Even though it’s been some time since you asked your question, I have a suggested workflow that might help you to achieve what you’re looking for, in case it is still something you’re trying to do.

In Zapier, create a zap that is triggered by a new inquiry in HoneyBook:
 

When the zap is triggered, part of the information that you receive from the inquiry is a field named “Contact Form Id”, which contains a string of numbers and characters:
 

This ID corresponds to a contact form ID in your account, which you can find in the URL when you go in to edit a contact form:
 

So now, all you have to do is map your contact forms name with their IDs from their URL in HoneyBook, set Zapier to keep this information for you when a new inquiry is coming (say in Google Sheets), and visit that data when you want to get some metrics.

Let me know if you find this useful!

This could also be useful if you need a unique field to key a spreadsheet update, such as updating an existing row when a payment comes in. I've been using email for this currently. The deposit updates correctly, but I'm still having trouble with the final payment updating. Also,  if the same client has multiple projects,  that causes problems. 

Rick, how about using the “File Id” and/or “Workspace Id” as unique identifiers for payments?
You get them when your zap is triggered by a payment, the file ID is the Smart File this payment originated from (so you can have a single line of payments per file that you add to with each payment). 
The workspace ID is a kind of “Project ID” identifier, if you have multiple payments within one project and would like to have one line per project and sum all of the payments from multiple files in it.

It means your sheet is not client-based but project/file based, but I believe you can later aggregate information per an email address if you want.​​​​​​​