I am trying to activate a zap, but I can only select Dev app version in Zapier. Anything I am missing? App is already live
1 Like
Currently have the same issue. Ever figure out a fix for this?
Are uou trying to make a POST in Bubble thru Zapier?
Iāve done this before with another app, but remember having an issue with the Live version displaying on Zapier.
Basically, in my app, I have a user click submit and it creates a record on AirTable. Then if they do something later in the app, say click a button, I want to trigger a Zap to update something on their AirTable record. I know exactly how to do the Zap, I just canāt get the Live App Version to show 
Essentially, the Zap would be:
Bubble (New Workflow Trigger Event) ā AirTable (Search for Record, when I create the record on AirTable, I add the Bubble ID so itās able to find the record I want) ā AirTable (Modify Record).
Did anybody have any joy with this?
Iām experiencing the same issue re: Development Version is not transitioning to Live.
@ken and @nomadinseoul I just spotted you on another thread with the same problem.
Did Bubble manage to resolve the issue?
1 Like
Same here. Makes me think that the new Zapier integration isnāt quite baked. Seems to work fine in Dev, but then going to Live it craps out. You can make it work temporarily by recycling it, but it doesnāt seem to last.
1 Like
Did anyone find the solution? Having the same issue hereā¦
When I contacted Zapier about this they said:
as long as you have your Zaps built and set up in your selected development version, you can simply deploy to live for them to work in your live Bubble environment as well. And for further clarification, it is expected that you wonāt be able to select a āLive versionā option in the dropdown on Zapierās side.
1 Like
3 Likes
Youāve had more luck than me. I ended up ditching Zapier and building all the API Connectors instead. Far more reliable and instant - not to mention cheaper!
1 Like
I guess, i could ditch Bubble and build code too, but i far too impatient for that 
So trying to find workarounds
Annoyingly this is the same for me. Notably, the Zap built in the Deve environment does get triggered from my Production environment, but this means that I cannot set up Deve versions of the Zap alongside Production versions (which would be nice for testing even once the system has gone live).
I could not work out how to manually change the source to āliveā using the Custom option in Zapier. Does anyone else have any ideas to share on this?
It worked for me following this strange workaround below:
1 Like
Just tried it and it seemed to work. Very odd.
Any solutions here? Iām struggling with the plugin as well.
Sorry Mary - tbh I canāt even remember what I was trying to use it for at this stage!
Two years later and I ran into the same problem. This worked for me.
Hi! I had the same problem today and solved it by working on the development version and then simply publishing the zap. It automatically goes to the live version.
I found this by reading this document from Bubble resources: Zapier | Bubble Docs
I copy the solution described in the document below:
Search for an App ID, such as āzapier-demo,ā and select a version for the application, either development or a custom branch name. If you would like to use this Zap in the live version of your Bubble application, first build your Zap and set it up in your selected development version. Once you deploy your Bubble application to live, your new Zap will work in your live version.
Hope it works!
Thanks!
Following up on this, I tried setting the app-version to custom āliveā on Zapier setting and it did not work. It seems safer to set app-version to development or custom branch, then deploy the zap and workflow and hope it works.