I’m working with a Zapier integration that connects to Stripe payments. The problem I’m running into is that I can only see the payment amount coming through, but I need more detailed information about what was actually bought.
Specifically, I want to capture things like the item ID, name of the product, and other purchase details. Right now I just get the price, which doesn’t help much when multiple items cost the same amount.
This makes it really hard to set up proper automation on my end since I can’t tell which specific product triggered the payment. Has anyone figured out a way to pull this additional product information through the Stripe-Zapier connection? Any workarounds or settings I might be missing?
This happens because Stripe doesn’t include line items in basic payment events by default. I’ve run into this same problem several times. Your solution depends on how you’re processing payments. If you’re using checkout sessions, switch to the ‘Checkout Session Completed’ trigger instead of the standard payment one. This gives you the line_items object with all your product details. Just expand the line items in Zapier to grab product names, IDs, and quantities. Another approach that’s worked great for me: set up custom metadata fields in Stripe during checkout. When you create the payment intent or session, dump your product info into the metadata object. This flows through to Zapier every time and you control exactly what gets passed along. Basically, Stripe keeps payment data separate from product data on purpose. You need to either use the right trigger or set up metadata to get what you want.
Yeah, this is a super common issue with Stripe-Zapier setups. Zapier’s native Stripe integration just can’t handle detailed product info well.
I’ve hit this wall multiple times. You need a more flexible way to handle Stripe webhooks and actually parse all the product data.
Ditch Zapier’s restrictions and set up a proper webhook handler instead. It’ll capture everything from Stripe payments - full payment object with line items, product IDs, names, quantities, metadata, the works.
Then process however you want and send to your other tools. Complete control over data extraction and flow.
I’ve built this setup several times - works way better than fighting Zapier’s limitations. You can even add custom logic for different product types or pricing scenarios.
Latenode makes it straightforward since it has native Stripe nodes and handles webhooks easily. Just connect the Stripe webhook trigger, add some data transformation, and route wherever you need.
yeah, definitely check that trigger! “invoice payment succeeded” gives you way better details. and like you said, if your product metadata isn’t filled out right, it won’t show up. good luck!
I encountered a similar problem while configuring my integration. Instead of using the ‘New Payment’ trigger, switch to ‘New Invoice Payment Succeeded.’ This allows you to access detailed line item data, including product names and IDs. Additionally, ensure that your Stripe setup is utilizing actual Product objects rather than just Price objects, as the metadata won’t appear without proper configuration. Keep in mind that subscription and one-time payments deliver product information differently, so it may be necessary to create separate Zaps to capture all relevant data effectively.