Browsing around the community it doesn’t seem like Zapier has an effective solution for managing multiple environments.
One stop-gap I’ve implemented that could ease the pain for those who have control of both the inbound and outbound data could be to simply introduce a “CONFIG” table with the appropriate values for the given environments.
I take my payload and embed an “$env” into the body, then look up the configuration in the CONFIG table, using the pre-configured values from the config table I point the rest of my integrations accordingly.
I decided against having multiple tables for tracking the full workflow and opted to instead add the “$env” value as part of the lookup key for the time being
Not perfect as changes to the workflow impact all of my environments simultaneously, but it beats retesting a 76-step workflow every time I want to make a small change and push it to my environments.
For those without the ability to change the body can also create multiple ingress zaps that act as proxies and simply mutate the request body before forwarding it to the main pipeline. Very clunky for a simple config switch, but at least gives some move forward options.
Want to see if anyone else ran into something or encountered any issues with this approach.
I’d also like to throw my hat in for something akin to the system variables feature but for environments
