This is one of the reasons I don’t use Zapier- it doesn’t support webhook responses. Make does, n8n does, pretty much any other solution does.
Ideally, you’d have JS handle the submit to the action ( the automation webhook ), wait for a response, and then have the slug needed to form the redirect.
Given that you took a different path, I’d probably so something like this;
- Pre-determine the slug. You manufacture it client-side, can be a UUID or MUID or one-way-crypto email hash, whatever. Pass that to the webhook.
- Redirect the user to a /loading page with a Please wait animation. Pass your unique token on the querystring. Run a script that forms the path from that token, and pings it every 500ms to see if the page exists yet. Once you get a 200, redirect the user there.
Or use an email flow-
- Require the user’s email in the form
- Pass it to the automation, have the automation also send an email to the user
- On submit, you thank them tell them to check their email for the link