 Hello, my name is Harshilagraval and I am an Auth0 Ambassador. In this video, I am going to talk about Auth0 actions and help you with connecting your Stripe account to Auth0. A user will sign up to your app, they will be automatically added to Stripe as a customer. Now to get started, you will need to create a tenant in your Auth0 account. I have already set up a mine for this video. You will also need a Stripe account, so go ahead and sign up on Stripe. And lastly, we are going to use a low-code automation tool called Entend to connect the Auth0 actions with Stripe. Paying a low-code enthusiast, I love to create projects with minimal line of codes. So this is my Auth0 dashboard. And on the sidebar over here, you can see Auth0 actions. The Auth0 actions has two parts, the flows and the libraries. A library is basically a collection of actions. The first thing we want to do is build a custom action and then we will add it to the flow. So we are going to click on build custom. Give this a name of call, and it ends with a book. Now we want to run this when a user registration is complete. And we can leave the runtime to node 16, while this is the recommended runtime. Now the wonderful thing I like about Auth0 actions is that you can import NPM modules. So let's go ahead and add XEOS, and we are going to use the latest version. Now that we have XEOS installed, we can go ahead and add it in our project. I'm going to define another constant, which is going to be the webbook URL that we are going to call. We are going to get that URL in just a second. We will make a request to that URL, but this is going to be a post request. And we want to send in the data of the user. Now that we have the setup and the actions, let's go ahead and get the webbook URL. I have an editor running locally on my machine, and because I wanted to use webbooks, I started an editor with a terminal. I'm going to add the webbook node. And in here, I'm going to change the method to post. For stronger security, you might want to add some kind of authentication to this webbook, so it can be a basic auth or a header auth. Now you can pass on the header or the basic auth information with your XEOS request. For the purpose of this video, I am going to just skip that part. The other thing is, we can customize this path, so let's just call this signup. And then I think it looks good currently because we are trying to test it and we are building it out. I'm going to use the test URL, copy it, save this workflow so that the webbook gets registered in an attend, and I'm going to come back to all zero actions and paste in my URL. Now that I have everything in place, I can go ahead and test this from within the actions. But before doing that, let's execute our workflow. And now we are going to run this, and you can already see, we have a payload data in here that is a sample data that all zero users for the test. It looks like the test result was a success. Let's check it on an attend. So if I switch to the JSON view, over here in the body, we have all the information that we need. This looks good. For the time being, let's just go ahead and deploy this. I'm going to click on deploy, this is going to deploy our action. Now that our action is deployed, I'm going to go ahead and close. Go to post user registration, and in here, I can drag and drop the flow. You can have multiple actions, and you can decide the order in which you want to run that. Let's apply this and go ahead and test it out in the real use case scenario. I'm going to go to get started, and over here, there is this beautiful option that allows me to try out the function. I'm going to go to try out. I'm going to sign up the user, and I'm going to gain, execute this workflow. I have to run it every time because I'm in the test environment and not on the production environment right now. So let's just call this, hey, I did it, test.com, and give this a wonderful password. If I come back to any time, we see that we have this information now coming in. That's fantastic. We got the data of the user when they registered in any time. Now, the next step is to move this data to Stripe. Now, there are a couple of steps that you can add in between some kind of functional logic that you want. So for example, you want to add the user to Stripe only when the email is verified. So you can add, and if not, which would check if the email is verified or not, and add that user to Stripe. There are a lot of options that we can do, but let us just go ahead and right now add the user to Stripe. Now for Stripe, I have a test account already created. I have enabled the test mode, and I am using that. I don't want to use it in my production environment for Stripe. And right now, in the customers, you can see that we don't have any customers. When I come back to any time, select the customer resource, click on create, and in the name field, because we don't have a name for the customer yet, I am just going to simply use the email address that we got from R0. Similarly, I am going to add a metadata, which is going to be R0 ID. This will help me identify the user if I ever want to check it against my R0 database. So this is the user ID, and then the email address. If I execute this node, we'll get a success message from Stripe with all the information you can see that our customer is now logged into Stripe. And if we go to Stripe dashboard and refresh the page, we would see our customer information in Stripe. So this was a quick overview of R0 Actions and how you can quickly connect R0 Actions with a lot of other APIs out there with NIT and IRO. If you want to learn more about the R0 Actions, I suggest you take a look at the R0 Actions documentation. It has tons of examples to help you get started.