This guide will teach you how to automatically update a Web3 based CRM (in this case, Holder.xyz) once you have a new signup to your dapp.
Holder is a CRM and marketing automation platform built uniquely to handle web3 and wallet data. With Holder + Dynamic, you can:
This guide builds on the serverless guide, so you should have already completed that guide and have a working serverless function. It also assumes you already have a Holder account.
For Holder.xyz, you’ll need to follow a couple of steps in order to get the token you’ll need to authenticate with the API. The fastest way is to follow this guide: https://docs.holder.xyz/holder-api/authentication. Come back here once you have your token!
You’ll be passing this in the header of API requests like so:
The choice is yours as to which library you use, we will use Fetch here.
First we need to know our base URL, which is https://api.holder.xyz/
. We will be using the POST
method to create a new user, and we will be hitting the /contacts
endpoint. The full reference for that endpoint is here.
We need to pass a primaryIdentifier which in our case will be email, and a value, which is the email itself. So putting it together it will look something like this:
Going back to our Serverless guide at Step 3, all we have to do now is add in our Holder function call:
You can then test and redeploy your function as in Step 4 of the serverless guide, and you’re done!
You should see a new contact in the Holder app like so:
The next step you might want to take is to update the contact if the user adds more details to their Dynamic profile i.e. wallet addresses etc. We will cover this in a further guide, so stay tuned!
This guide will teach you how to automatically update a Web3 based CRM (in this case, Holder.xyz) once you have a new signup to your dapp.
Holder is a CRM and marketing automation platform built uniquely to handle web3 and wallet data. With Holder + Dynamic, you can:
This guide builds on the serverless guide, so you should have already completed that guide and have a working serverless function. It also assumes you already have a Holder account.
For Holder.xyz, you’ll need to follow a couple of steps in order to get the token you’ll need to authenticate with the API. The fastest way is to follow this guide: https://docs.holder.xyz/holder-api/authentication. Come back here once you have your token!
You’ll be passing this in the header of API requests like so:
The choice is yours as to which library you use, we will use Fetch here.
First we need to know our base URL, which is https://api.holder.xyz/
. We will be using the POST
method to create a new user, and we will be hitting the /contacts
endpoint. The full reference for that endpoint is here.
We need to pass a primaryIdentifier which in our case will be email, and a value, which is the email itself. So putting it together it will look something like this:
Going back to our Serverless guide at Step 3, all we have to do now is add in our Holder function call:
You can then test and redeploy your function as in Step 4 of the serverless guide, and you’re done!
You should see a new contact in the Holder app like so:
The next step you might want to take is to update the contact if the user adds more details to their Dynamic profile i.e. wallet addresses etc. We will cover this in a further guide, so stay tuned!