I am posting this after waiting for over a week for a response from Support (seems to be par for the course). Zapier’s rollout of Gravity Forms App Event 2.0 has been abysmal. Not only was there no announcement of the deprecation of 1.1.0, the complete removal of 1.1.0 combined with the forced migration to 2.0 when a GF trigger is edited has caused us a lot of trouble.Our issue is two-fold:Zapier Add-on (ZA) 4.0 does not work when trying to submit partial entries to Zapier. This worked without issue with ZA 3.3. The forced migration to Gravity Forms App Event 2.0 has left 2 of our Zaps unusable as they never get triggered and we can not roll them back to 1.1.0.We have contacted GF support and are working with them regarding issue number 1 (others are having this issue as well). However, in the meantime we have been trying to get a response from Zapier regarding reinstating 1.1.0 alongside 2.0 so that we can get our Zaps working again. While we understand that 1.1.0 is deprecated, it is still in use for the majority of our Zaps and works fine. It should have remained available until all bugs with Zapier Add-on 4.0 and the associated REST API had been worked out.

Hey everybody! Just posting aquick update here to say that this issue has been closed. If you’re still having problems, your best bet would be to contact the Gravity Forms support team. They can troubleshoot the issue to see if you’re running the correct versions of WordPress, Gravity Forms and the Zapier Add-On.

Best answer

Gravity Forms 2.0 Issues

3 years ago
10 March 2021
26 replies
1580 views

J

Userlevel 1

Joshua J
Beginner
2 replies

I am posting this after waiting for over a week for a response from Support (seems to be par for the course).

Zapier’s rollout of Gravity Forms App Event 2.0 has been abysmal. Not only was there no announcement of the deprecation of 1.1.0, the complete removal of 1.1.0 combined with the forced migration to 2.0 when a GF trigger is edited has caused us a lot of trouble.

Our issue is two-fold:

Zapier Add-on (ZA) 4.0 does not work when trying to submit partial entries to Zapier. This worked without issue with ZA 3.3.
The forced migration to Gravity Forms App Event 2.0 has left 2 of our Zaps unusable as they never get triggered and we can not roll them back to 1.1.0.

We have contacted GF support and are working with them regarding issue number 1 (others are having this issue as well). However, in the meantime we have been trying to get a response from Zapier regarding reinstating 1.1.0 alongside 2.0 so that we can get our Zaps working again. While we understand that 1.1.0 is deprecated, it is still in use for the majority of our Zaps and works fine. It should have remained available until all bugs with Zapier Add-on 4.0 and the associated REST API had been worked out.

icon

Best answer by nicksimard 2 August 2021, 19:32

View original

Show first post Hide first post

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

26 replies

1
2

Page 2 / 2

J

Userlevel 1

Joshua J
Author
Beginner
2 replies
3 years ago
11 March 2021

Thank you for your response, Nick. I do not know why we are not receiving Zapier’s responses - they are not being flagged as spam.

I understand that the migrated zaps cannot be rolled back to 1.1.0. I was more interested in having the option to use 1.1.0 alongside 2.0 to create new zaps. I know during the beta phase of 2.0 that both were provided (image from current documentation for GF’s Zapier Add-on 4.0):

I could submit another ticket, but at this point I am not sure it would do any good. As I mentioned, we have determined the issue to be with changes introduced with GF’s Zapier Add-on (ZA) 4.0 that is preventing partial entries from being submitted to the zap as they were in ZA 3.3. The zaps are never triggered so the history shows no change. Thus, this is why we request the restoration of the 1.1.0 app event so that the two non-functioning zaps could be recreated. Combined with rolling back to Zapier Add-on 3.3 all of our zaps would be functional again while GF works out the problem. Apparently, GF support thinks this is something within the control of Zapier since they asked us to request this.

1
2

Page 2 / 2

Sign up

Use your Zapier credentials

Log in to the Community

Use your Zapier credentials

Scanning file for viruses.

This file cannot be downloaded