1. What is your feature/integration request?
After using the
Send to an API, I would like to store/send the API’s response.
2. What problem would this feature/integration solve?
As described in this thread, currently the only way to do this is to use the
Enrich with an API step. Unfortunately, that step is too sensitive and will run anytime we update something upstream in the flow (also as acknowledged by Brian in the thread).
We send to the Zoom API to create webinars and meetings. Then, we want to obtain the Zoom Meeting IDs from the API’s response after they have been generated and then send them to a Google Sheet.
Additionally, while not our primary concern, this feature would also seem to help with this situation of storing error handling.
3. How do you solve/workaround this problem today?
Enrich with an API is currently the only method that would make this possible. Unfortunately, we have inadvertently triggered the flow multiple times, thus creating hundreds of duplicate webinars and meetings unintentionally.
Enrich step triggers even without pressing “Run Flow.”
Worse, the duplicate webinars and meetings do not flow all the way to the last step of sending to the Google Sheet, so we are not initially aware of them and we have no way of programmatically deleting them using the Zoom API, since the Meeting and Webinar IDs have not been captured from the response, and Zoom’s API requires the ID in order to take any action.
As a result, Brian’s suggestion below doesn’t work, if we can’t capture/record/store the Zoom ID that was generated from sending the data to the API:
The other way to get those IDs would be to use a separate flow and pull all of your customers from that API into Parabola, and then send those to your other service.
We’re hopeful this new feature would be helpful to many in the community to simply capture/store the API’s response after sending to an API.
Thanks for your consideration!