Ah, gotcha!
In that case, yes… your initial thought of using Make (Integromat) was the correct approach
This won’t be uber secure, but it’ll most likely be good enough…
The /embargo
page will need a simple, native Webflow form on a static page, allowing them to enter their secret code.
You’ll want to use Make (Integromat) for this. If you don’t have an account, their free tier will do the trick.
If the secret code is always the same here’s a screencast for you:
It gives you most of what you need, but not all of it.
Instead of creating a new CMS item as shown in the screencast, you’ll need to hard code the CMS item ID you want to send them to.
In your case:
/releases/[release_that_has_secretstory_password_attached]
Anyone can access the url with the Item ID, but those Item ID’s are long and random, so it’s difficult to guess.
Also, add the secret code they enter to a filter after your Webhooks modules (from the screencast above) to check for that.
On the other hand…
If you want the secret code to be unique for each journalist you’ll want to use something called a lookup table. Here’s a quick tutorial on that:
You’ll need to inject that into your workflow.
If this is all too much you’ll need to find a pre-canned solution that you can bolt into Webflow. I don’t know of any off hand.
Otherwise, feel free to ask question, I’ve got answers