Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hi All

 

This seems to be a recent issue as reported in the the Reddit Zapier Community (Changes to webflow integration issue)

 

I’m pretty used to Zapier and use it for sending data everywhere. However the new Zapier upgrade to Webflow means it does not do the following

 

  1. Does not fetch all the forms on the website
  2. Does not fetch forms that are in Webflow Components

For those that do not know - Webflow allows users to make repetitive elements like headers, and footers, newsletters into components. Then the user can add these components to other pages. Editing one instance of the component will edit them all. (Similar way how WordPress does it with Elementor).

 

Anyway, the new Zapier Webflow Authentication does not show forms that are inside the components. This is not good at all. A designer like myself may have a newsletter form in the footer (don’t most sites?). This is standard practice, but Zapier does not even see it on the list. 

Rather what happens, is finds the instance of the form on random pages. For example the newsletter form is inside a component (footer), but what Zapier finds is this: Contact page: Newsletter form, About page: newsletter. 

 

In Summary there is something very wrong on the Zapier side which means the newsletter forms or any form in a component cannot be seen by Zapier. 

 

Additionally, what I do not understand is this: The newsletter form has a unique ID. This ID is the same no matter what page the newsletter form is on, as its the same form, same ID just different page. Zapier does not find this form ID, just others. 

 

Can support help please? This is quite a big issue for the Webflow community that have forms in components. 

Hi @jambajamba,

Welcome to the Community! 🎉

It looks like we have a feature request for New Form Submission - Trigger by form component instead of the form instance on the page. I have added your contact information to the feature request. That does a few things:

  • Bring this to the attention of the integration developers
  • Help track interest in this feature being implemented
  • Allows us to notify you via email if this feature becomes available in the future

While I don't have an ETA on when this feature might be implemented, we will notify you via email if it is!

In the meantime we have a workaround regarding this one here:

Workaround

  • Use a catch hook for the trigger.

  • In the site settings, go to the apps and integrations page, and add a webhook.    

  • Select form submission for the trigger type and paste the URL from the catch hook trigger

  •   

  • Use a filter in the Zap to filter on the Payload Name field, which is the form name.

Hopefully, this helps.

Hi, we have the same problem and we ask you to fix as soon as possible.
Thank you

I have the same issue. Thanks for the workaround @ken.a, this helps for now. But I would also very much prefer the zap to work again like it did with the older webflow connection. So can you put my contact information to the feature request too? Thanks. 

Hi @Quanta Club Milano and @simpu.design,

I have added you both to the feature request. We will keep you updated via email once it has been implemented.

I appreciate your patience and understanding.

Can you add me to the feature request as well? And is this the same fix for the ‘New zap for each instance’ question that’s on this forum as well?

Hi @daandvn,

I have added you to the feature request. We will keep you in the loop via email once the feature has been implemented. Regarding your question, I haven’t really tried out this workaround myself, but yes this workaround is a fix for the new Zap for each instance issue.

Thanks you for your patience and understanding.

Can you add me to the feature request as well? And is this the same fix for the ‘New zap for each instance’ question that’s on this forum as well?

@daandvn as far as my experience goes it solves that problem too. The disadvantage is that you need the pro version of Zapier because it is a multi-step zap.

Reply


Terms & Conditions