This is the URL generated by ngrok with /email attached at the end. Next you have to enter the destination URL for your webhook. If you are doing this for the first time you will only see the domain that you verified above. This is a dropdown list that shows all the domains that you have verified with SendGrid. Next you have to select your domain name. If you want to receive emails on your top-level domain it can be left empty. This can be any subdomain that is available on your domain. In the next screen you can optionally enter a subdomain on which you will be receiving emails. Now that you have a publicly accessible URL, go back to the SendGrid dashboard and under Settings select Inbound Parse, then click on “Add Host & URL”. The output should look something like this: This is telling ngrok to create a “tunnel” from the public Internet into port 3000 in our local machine, where the Express app is listening for requests.
Busboy npm code#
With the Node.js code running, open a second terminal window to start ngrok as follows:
Busboy npm install#
If you haven’t yet, install ngrok on your system. We are going to use a tool called ngrok to create a public URL that SendGrid can use to forward requests to our locally running application. With the Express application running, we just need to connect it with SendGrid to be able to receive emails. Configure the SendGrid Inbound Parse webhook Leave it running for now, and we will make it accessible on the Internet. The application is now running and waiting for incoming requests, but it is only reachable from your own computer because we are running a development server. You can run this code with the command node index.js or npm start in your terminal. You can review the complete list of email parameters in the SendGrid documentation. SendGrid will invoke this route each time an incoming email arrives, sending all the information about the email as a standard form post, which we are using multer to parse so we can access it in request.body. The application defines a single web route attached to the /email URL.
0 kommentar(er)
