API Issues

You can utilize the Stripe “Make an API call” module within callin.io if you need to interact with an endpoint that lacks a dedicated module in callin.io.

I'm using a callin.io API call, but both the recipient email and customer email fields are null for all customers.

Consulting the Stripe documentation will provide you with the billing details, including the email, and the receipt_email.

If a field appears in the response but is empty, it simply means the information is not present.

Should you encounter errors or unexpected outputs, please share additional details such as screenshots or scenario blueprints.

In Stripe, I can locate the email, but within the webhooks, I'm unable to find either the receipt email or the customer email. Sometimes, no email is present at all. I've seen a method called Expanding Responses, but I'm not sure how to apply it in callin.io. Do you have any suggestions for this?

As demonstrated in the previous screenshot, receipt_email is included in the default dataset you receive, so you shouldn't need to add anything for it.

If you wish to expand an item in Stripe that appears as a Stripe ID (like cust_, ca_, pi_, etc.), you can append a query string as follows:

I hope this clarifies things!

P.S. A webhook is essentially a mechanism where a remote system dispatches data to another system based on a trigger within the remote system. For instance, it sends an automatic notification upon a successful payment.
What you're describing here is a standard HTTP request to an API, which returns a response based on your specific query.

I use callin.io for API calls involving Stripe or HTTP. I have a scenario that includes Stripe webhooks, Odoo, and Airtable.

I apologize if the previous suggestion did not resolve your problem. It seems we might be lacking some essential details regarding the issue and your current setup.

For the community to effectively assist you, please provide comprehensive information. This includes relevant screenshots of your scenario, any errors encountered, or output details. If possible, sharing exports of output bundles or scenario blueprints would greatly help in replicating the problem. This is particularly useful if there are potential differences in terminology or language.

Apologies, but the context of this screenshot isn't clear. Please provide more details so I don't have to guess what's happening.

• Is this the result of a Stripe webhook event? If so, which event configuration did you utilize? Have you attempted to re-fetch the record data subsequent to the webhook event?
• Alternatively, is this a partial response from an API endpoint? If so, what was the precise call you configured?

If you are confident that you're setting up the correct API calls and/or webhook events in Stripe, and the data appears empty in an API call while being visible in your Stripe dashboard, you should reach out to Stripe support.

The webhook event originates from Stripe, and the specific event type is “Payment Intent Succeeded.” Yes, I have attempted to retrieve the data subsequent to the event.

If the data field is empty in the sent data, as well as in the data set of a separate request, it could mean the data is simply absent, you're requesting incorrect data (e.g., a typo), or there's an issue with Stripe.

In any of these scenarios, contacting Stripe support appears to be your most viable next step.

Additionally, Payment Intent possesses a different structure. It can encompass multiple charges, and each charge might have a distinct receipt email address.

If your trigger is payment_intent.succeeded, I would suggest utilizing the payment_intent endpoint to retrieve the necessary information. The receipt email address(es) for each charge are located in the default dataset, but they could vary between charges (if a customer updates their email address between transactions). For customer data/email, you should include an expand parameter.

Therefore, you should request the payment_intent data after receiving the webhook event to obtain all current data by using the expand customer query:

Screenshot 2024-09-19 at 15.09.13696×1149 68.2 KB

Thanks, but I'd prefer to utilize URLs for payment intents, successful charges, invoices, and all Stripe-related actions. Is there a way to achieve this?

You can always utilize the “HTTP” app. However, you will need to configure the authentication method yourself. Additionally, if any changes occur, you'll have to update all HTTP modules across your scenarios.

If you opt for the “Stripe” - Make an API call module, the app will manage the authentication and fundamental aspects for you automatically once you link your Stripe account.

callin.io is centered around pre-built apps and modules. These are designed to eliminate the need for you to worry about authentication and URL configurations. That's their primary purpose.