#gmgarrison_webhooks
wise ospreyBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1324393085496590337
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
lusty talon
Right now, I can run this command "stripe listen --forward-to https://iamt-app.test/stripeprocessing" and I get a CLI session but when I try stripe trigger payment_intent.succeeded, nothing happens.
lucid solar
Hello
We generally don't know much about integrations created through third-party platforms (I assume you're using a plugin for laravel to connect to Stripe?)
Have you tried looking into your webhook events log and see if there's an error there? https://dashboard.stripe.com/test/workbench/events
lusty talon
Well, aside from any integrations I don't think I'm actually successfully generating any test events from the CLI
There's nothing from today in the dashboard for test events
If I can just reliably generate test events from the CLI, I'll be thrilled
lucid solar
If you're not seeing any events in your logs after using trigger command (assuming the command succeeds), then you'd want to check if you're logged into the right Stripe account.
Can you share the event ID CLI generated with trigger? evt_xxx
lusty talon
I'm trying to follow these steps:
But running the stirpe listen command does not return me to a command prompt
Am I just supposed to leave that command running and start a new terminal sesssion in order to run the stripe trigger command?
lucid solar
yes
listen command should stay running and you'd use a different terminal session to trigger
lusty talon
Trying that now
Ahh bingo!
Is there a way to configure metadata inside a test event?
Or an easy way to copy a real historical event and use it as a test event?
lucid solar
You can use --override or --add flags to customize events - https://docs.stripe.com/stripe-cli/triggers#customize-events
Or an easy way to copy a real historical event and use it as a test event?
if this is in test mode, you can try resending it.
lusty talon
Okay, great
lucid solar
We have the complete reference here - https://docs.stripe.com/cli