AI to build Wappler API Actions for Stripe Webhooks?

[GraybeardCoder]

It was fun for all of 5 minutes reading Stripe's API docs and trying to build my webhooks in Wappler. My first attempt at integrating Stripe with my site using Wappler, was to use the built-in Wappler components. As Stripe continued to update its object models for different events, the Wappler components became less reliable. I'm now rewriting and testing my webhooks using Wappler's API Action component. However, if there's an AI tool that can help this process, I'd LOVE to know.

[Teodor]

@GraybeardCoder

My first attempt at integrating Stripe with my site using Wappler, was to use the built-in Wappler components. As Stripe continued to update its object models for different events, the Wappler components became less reliable.

can you please share more details about what's outdated so we can improve it?

[GraybeardCoder]

Stripe Webhook Subscription Updates & $_POST Data Model Differences

If a customer changes their subscription plan, Stripe sends my endpoint an object model that contains "object" and "previous_attributes". The "object" contains the new subscription info while "previous_attributes" contains the old subscription info. [Screenshot 2025-01-16 at 6.03.54 PM] The existence of "previous_attributes" tells me there was a change to the subscription product (like an upsell) versus some other customer.subscription.update (like a cancelation or pause). In Wappler, the cu…

Wappler Stripe Components & Outdated Data Structures

I'm finding more built-in Stripe components are not populating their data structures in my API's. This time, it's the simple Retrieve Customer component in Wappler not populating the customer's email address. Wappler's object model differs greatly from Stripe's API reference documentation. Wappler's model, which is sorted alphabetically in the GUI, looks like this: [Screenshot 2025-01-16 at 10.57.45 AM] Stripe's current object model looks like this: [Screenshot 2025-01-16 at 10.58.41 AM] T…

Wappler Webhook Stripe Checkout Session Data Structure Doesn't Match Stripe Response Body

Wappler v6.7.3 Webhook: checkout.session.completed The "Line Items" section in Wappler's stripe.checkout.session data structure doesn't match what is being sent from Stripe's checkout session API call to my webhook. Stripe returns a "line_item_group" which is not available in Wappler's dynamic data picker. Wappler's structure offers "line_items", which is actually a child of Stripe's "line_items_group". So the issue I'm having is not being able to access anything under Stripe's "line_item_grou…

[Antony]

I’ve rewritten the Wappler code which runs when a Stripe Webhook is received… it ignores the endpoint key and just checks if the subscription ID exists in my database… then it grabs the bits I need from the (object) structure and stores the main info to be processed with a crontab later.

It’s PHP based, but happy to share the details if it would be helpful!