Hello @marcelg,
The webhook itself will work even after June 1 but is still associated with the Basic API Token (legacy) connection which might cause you issues in the future even though you do not use any other modules.
We would recommend creating a very new RAK connection (see screenshot below) and then creating a very new webhook URL.
For anyone trying to list their scenarios using Stripe, I created a scenario that does it for you and logs it in Airtable.
It also displays the folder name, scheduling type, and other used packages.
Remember that the limit for the ‘List Scenarios’ module is 400.
If you have more than 400 scenarios, you might have to tweak the scenario to catch all of them.
Here’s the blueprint:
listScenariosUsingStripe.json (17.1 KB)
Outline:
Stripe filter:
Airtable mapping:
Enjoy!
@Michaela - When creating the restricted API key in the Stripe, do I set the permissions to ‘Write’ (or ‘Read’ if no write permission) for all the listed resources?
Hello @andyc
When creating the restricted API key, please set the permissions based on what you want to achieve with your Stripe automations. “Read” permissions let you view the data, while “write” permissions enable you to input or update data.
Thanks @Michaela.
As per @Bert_Schoofs comment above, is there anyway to see what scopes were set for the previous webhooks? Or a way to check without having to guess what they were?
Is there any possibility of updating the connection associated with a webhook in Make?
Adding a new Stripe webhook in Make will create a whole new webhook in Stripe, which will lead to duplicate webhooks in my Stripe workbench.
@andyc @Bert_Schoofs If it’s not directly visible in Stripe, you can use the “Make an API Call” module to call the following API endpoint and get a list of webhooks and their subscribed events:
@BenChapman Unfortunately, updating a connection is not possible.
