"Stripe > Send Invoice" Integration

@david mentioned moving the “Stripe > Send Invoice” integration from Business to Pro a few days ago and I’m wondering if anyone can speak to what happens after using this action? I’ve built my own version of it in Make but am having trouble getting the invoice status back into glide.

Any tips/advice?

Why not start a free 14-day Business trial and try it yourself?


Error “Send invoice: Mandatory inputs not provided”

Screenshot 2023-03-21 at 3.55.54 PM

Looking into it!

1 Like

Please make sure your Currency column has a value, and also go to your apps Settings → Integrations and make sure your API key is set. We have a bug right now where the API key does not always properly save.

1 Like

Thank you @Jason, I’ll check first thing in the morning!

The issue was the API key. Now that I have successfully sent an invoice my question is what are we supposed to do about creating a customer in glide since that is required before sending an invoice. And once the invoice is paid, how are we supposed to get that information back into glide?

It seems like we are now responsible for building out the “Glide Apps Classic” “Buy Button” ourselves. Do we need to set all this up in Make and have it write to a google sheet?

Apologies for all the questions but I’ll be migrating my Classic App over to the new App and the “Buy Button” was a HUGE part of making my business work. I just need to find out what Glide recommends we do to make the “Buy Button” flow work in the new “Pages/Apps”.

Thanks so much for anyone who can help.

1 Like

The plugin will automatically create a customer for you if you don’t provide one.

As for feedback when the invoice is paid, there is no mechanism for that… yet.

1 Like

Thanks for the feedback. I would highly suggest updating the “required fields” and “hints” for anyone currently using the integration. I will come back to it once it provides status updates or I learn how to get those updates into glide. Thanks a ton.

Yeah there is a bug in the “required” validation format.

FYI: I just downgraded my plan back to pro from business and the stripe action still works. Not sure if this will continue for the “trial” period or if the integration has already been moved to “Pro” plans and the “Business” tag is still displayed on the integration panel.

It will stop working before the beta period ends.

Hi I am having the same exact questions in using this new integration, doesn’t seem to be documented at all.

I use the Buy Now button in an App and trying to replicate the same things in Apps but not getting it to work. Will the button send the invoice to the users email or will it open in a new link?

Any help would be appreciated.

Why not use stripe payment links? Saves you having to have the user open their email, then go back to your app, etc

1 Like

Tell me more about this magic you speak of. Also, how do I get proof of payment back into the app?

So, a lot will depend on what you are selling, etc. But at the top level it works like this. Let’s assume you’re selling a membership. That is, you need someone to purchase a digital subscription to access the rest of your Glide app (not just the “Buy subscription” screen). You set up a product in Stripe. Set up a price for the product (your monthly subscription), and a payment link for the price (you do all of this in the Stripe dashboard, no code whatsoever).

Stripe payment links can be personalised for every customer. You do this by including a piece of customer information at the end of the payment link URL as a URL parameter (or a query string). What this piece of customer info will be depends on your Glide plan. If you’re on a Pro plan and you collect actual email addresses - pass the email address through. If Glide obfuscates them, you can pass the Row ID from the Users table as a client_reference_id URL parameter.

To personalise the payment link for each customer in Glide, create a column in your Users table that dynamically personalizes the payment link with the user’s email address or the row id (if you hold your user data in Glide tables, you’ll need to pass the Row ID due to the limitations of Glide Tables API). You can use the “template” or “URL builder” fields. This link is what you add to your buttons in Glide to make them… “Buy buttons” :wink:

Once the customer purchases something using this personalized payment link, whatever info you passed through as the URL parameter will appear in the transaction’s checkout object in Stripe. So you can capture it in Make (Watch events => Checkout completed) and then…[ta-da]… pass the info to the Users table in Glide. If you’re using Glide Tables for your Users data, you’d need to use Glide Tables API (use an HTTP module in Make). If you’re using Google Sheets or Airtable - call up the relevant module in Make.

Just don’t forget to change the visibility of the rest of your app in line with the purchase info from your customers that you wrote back to the Users table.

Suppose you’re using a recurring membership model. In that case, there are a few extra steps you’d need to take to link recurring billing (or cancellations) to your Glide customer, but all more than doable with Stripe, Make, and [Glide tables; Google Sheets; Airtable].

Using this setup you can sell memberships, credits, etc. The only limitation is that you probably won’t be able to sell a bazillion of products this way. But if you’re selling access tiers or credits, this will more than do.

You can further automate things by creating a “Products” table and linking a Price ID in Stripe to the membership tier you’ll write back to the Users table when someone purchases it.

Feel free to hit me up if you need a detailed walk-through.



I would love to schedule a call with you asap! My use case is super simple but learning whats possible is worth whatever it will cost. jonathonkohn@gmail.com

Responded to your email :slight_smile:

Meanwhile, I think I also figured out how to build back ecommerce functionality for a use case where you have a lot of products to sell (not just a few memberships). Slightly different workaround, but just tested it and it works! Shame I personally don’t have a use case for this…yet.

1 Like

This is interesting. I assume this is something exactly the same as what PayHere offers?

PayHere was some sort of a workaround built on top of Stripe that we have used extensively in the past few years to offer personalized payment links and subscriptions in Glide.