#phernanz_webhooks

1 messages · Page 1 of 1 (latest)

outer wagonBOT
#

👋 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/1444971150546571296

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

trim widget
#

👋
The event evt_1SZRORAPBfHnjwxg5wZFordw was delivered to your platform connect webhook endpoint we_1SSbp0EWWnCm2jogQoG7C56D

#

What is the issue you are facing ?

echo pivot
#

Thanks for providing that Endpoint ID (we_1SSbp0...). That is very strange because that endpoint does not exist in my Dashboard. It must be an old or deleted configuration.

I have attached a screenshot of my current Platform Webhooks settings. As you can see, the only active endpoint configured is we_1SZJNTE..., which points to my current n8n instance.

The issue: Stripe seems to be routing events to a non-existent/deleted endpoint (we_1SS...) instead of the one currently active and visible in my Dashboard (we_1SZ...).

Could you please help me understand why this routing is happening and how to force the events to the correct, active endpoint?

outer wagonBOT
trim widget
#

The platform Account is acct_1PxbwPEWWnCm2jog and the connect account is acct_1PxlfUAPBfHnjwxg

#

You are showing screenshots from the connected account I think

#

Can you share the webhook endpoint complete Id you are expecting the event to come in ?

trim widget
#

That webhook endpoint belongs to the account acct_1SMWDzEymNg9SU8W which is antoher account

#

The event generated belongs to the account acct_1PxlfUAPBfHnjwxg

echo pivot
#

"Here is the full information you requested to clarify the situation:

  1. The IDs involved:

Platform Account: acct_1PxbwPEWWnCm2jog (This is the parent platform).

Connected Account: acct_1PxlfUAPBfHnjwxg (This is where the payment happened).

Target Webhook ID: we_1SZJNtEymNg9SU8WOtSRgIvD (This is the one I configured in my Dashboard to receive the event).

  1. The Potential Mismatch (Investigation): I noticed something critical while gathering this info. When I view my Webhook we_1SZ... in the Dashboard, the URL in my browser shows I am logged into account acct_1SMWDzEymNg9SU8W.

My Hypothesis: It seems I might be configuring the webhook on the wrong Stripe Account (acct_1SMW...) instead of the actual Platform Account (acct_1Pxb...).

Could you confirm if acct_1SMWDzEymNg9SU8W is unrelated to the Connected Account acct_1Pxl...? If so, that explains why the event goes to we_1SS... (which likely exists on the real Platform account) and not to my new endpoint."

reef imp
#

hey there 👋 this makes sense

acct_1SMWDzEymNg9SU8W is a sandbox account, created for acct_1PxbwPEWWnCm2jog

so it is related to the platform, but it's separate in terms of Stripe Connect, so it's not related to acct_1PxlfUAPBfHnjwxg

echo pivot
#

That explains everything perfectly! Thank you so much.

I assumed the Sandbox account would automatically inherit the traffic from the Connected Account, but now I see they are separate contexts. I was effectively waiting for the event in the "wrong house".

Action plan: I will switch to the main Platform Account (acct_1PxbwPEWWnCm2jog) and configure the n8n webhook endpoint there. That should definitely solve the issue.

Thanks a lot for your time and for spotting the Account ID mismatch—that was the key. I’ll report back here only if I run into any unexpected trouble, otherwise consider this solved.

Have a great day!