Why would you build this?

We will be building this Vercel backend and Replit designed to receive data from FluxRPC’ webhooks of on-chain Solana transactions and using node-mailer to send emails containing info about these transactions. This will allow users to be notified of important transactions in real time, such as when they receive a payment or when a new NFT is minted.

Here are some specific benefits of this system:

Real-time notifications

Users will be notified of important transactions as soon as they happen. This will help them to stay up-to-date on their finances and be more involved in the Solana ecosystem.

Increased security

Users will be able to receive notifications about suspicious transactions, such as attempts to withdraw funds from their account. This will help them to track their assets.

Improved user experience

Users will have a more seamless experience when using Solana-based applications. They will be able to receive notifications about important events without having to manually check their accounts.

We believe that this system will be a valuable tool for Solana users. We are excited to see how it is used to improve the Solana ecosystem.

GitHub - Tidelaw/webhook-sms-email: Uses FluxRPC’s webhooks to send SMS notifications.

If following the below guide, feel free to ask for help in the FluxRPC Discord or check with the open-source repository.

Replit Version

Replit is a cloud-based integrated development environment (IDE) that allows you to write code, run it, and share it with others in real time. It is a great tool for beginners and experienced developers alike.

To create a Replit, simply go to the Replit website and click on the “Create a Repl” button. You will then be able to choose a programming language (javascript) and a template for your Repl. Once you have created your Repl, you can start coding right away.

Replit uses .env files to store environment variables. Environment variables are used to store sensitive information, such as API keys and passwords. They are not stored in plain text in your Replit, so they are more secure.

Replit Dependencies

The following dependencies are required to run our script:

  • nodemailer: This dependency is used to send emails.
  • express: This dependency is used to create a web server.
  • body-parser: This dependency is used to parse the body of HTTP requests.

To install the dependencies, simply enter:

Block Field

‍Now, we can start our express server to start receiving data from the webhooks:

Block Field

  1. The first line of code imports the nodemailer package, allowing us to send emails.
  2. The second line of code creates an Express web server where we will be receiving data from FluxRPC’s webhook.
  3. The third line of code imports the body-parser module which makes it much easier to parse data from our webhook.
  4. The fourth and fifth lines of code, configures the web server to parse JSON requests using our body-parser dependency.

‍We will now need to set up our Gmail API, as well as save these environmental variables to replit.

Gmail API Keys

First, follow this guide and acquire an App Password for Gmail, you’ll need to set up 2-Step-Verification as well. This is all we need to begin sending emails using node-mailer.

Setting up Replit environmental variables

To access replit’s .env variable menu, locate it at the bottom left of your replit client.

Block Field

‍You’ll now see it being displayed on the bottom right, where your terminal is.

Block Field

‍Simply enter the name of the variable e.g email_password where SECRET_KEY is, and input your values. receiver_email and sender_email are the two emails that will be used to send and receive the email, email_password in our case will be the password for the email you’ll be using to send it.

We can now start to receive data from our webhook:

Block Field

‍The web server is configured to handle HTTP POST requests to the /webhooks route. When the web server receives a POST request to the /webhooks route, it will extract the body of the request and display it to the console for you to test. The web server will then respond to the request with a 200 OK status code to let FluxRPC know we’ve received it so that they won’t send repeat messages.

Webhook Setup and Testing

In order to begin testing, simply click the Run button and a website should appear on the right.

Block Field

‍Don’t be alarmed by the error, our server only accepts POST requests so we will need to use FluxRPC to test. We can now head over to FluxRPC and set up a webhook.‍

Block Field

‍We’ll be listening to Mainnet transactions, of the ‘Enhanced’ type, these contain the description property that we will be sending as an email. Paste the link of the generated Replit server from before, in this case https://fluxrpc-webhook-sms-email.tidelaw.repl.co/webhooks and the wallet you wish to listen to. Make sure you include the /webhooks along with the Replit generated site!

You can now test it using this feature on the FluxRPC Developer Portal

Block Field

‍Which should return this:

Block Field

‍Here is a JSON file of the data we received from FluxRPC’s webhook:

Block Field

‍Notice that it is an array, in order for us to reference the object to send as a message, we will need to access the description property through body[0].description.

Email Integration

‍We can now integrate Gmail, allowing us to send an email containing the description of the transaction.  You’ll first need to configure nodemailer to the service, or type of email you’ll be using. Then, reference the .env variables we just set up, with the details of the email you’ll be sending from.

Block Field

We can now code the actual sending of the email, using the express endpoint we set up before to receive the requests. We first create an object containing all the relevant info that nodemailer needs to send the email, e.g a sender, a receiver, a subject (not necessary), and the body. This is where we will be inserting the actual transaction data by referencing the body object we received from FluxRPC’s webhooks - using the test data from before, we can determine how to access the description property.

Block Field

‍The completed code should now look like this:

Block Field

‍Congratulations! You should now be able to receive an email if you have correctly configured the .env variables and installed the right dependencies. If you’re stuck, feel free to send a message in the FluxRPC Discord for help.

Next Steps, Vercel Version

The problem with replit is that there is a cost in keeping this script up 24/7, one solution is to host a website on Vercel with only a backend, that will run constantly, at 0 cost. The setup is mostly the same, the only difference being where the .env variables are stored and a github repository.

First, you’ll need to fork this repository:

Block Field

‍We can now head to Vercel where you’ll need to make an account.

Then, head to the dashboard and add a new project.

Block Field

‍Simply add the environmental variables from before to the Vercel project:

Block Field

‍After deploying the project, you can now run the same tests**** that we did for replit, you will now be able to receive emails containing onchain transaction data 24/7 for free!