Hey Peter – Thanks a lot for the kind words! Much appreciated.
Totally hear you on the ParseHub step still causing issues – our engineering team is aware of the issue with the step, though I’m unfortunately unable to provide a good estimate on when to expect a fix. I’ll be sure to let you know if I hear an update.
I do agree we you about limitations with the API workaround. We are able to dynamically pass a
RUN_TOKEN to an
Enrich with API step, but do not have a good way of waiting to request data from a run until after the run has completed. This appeared possible using webhooks, however we’re unable to support their
Content-Type: application/x-www-form-urlencoded header in that request.
Hopefully we’re able to resolve the ParseHub step error while you work on developing the flow!
Will certainly keep you updated on the PATCH front as well
Thanks for your understanding and kindness in the community here Peter!