As mentioned, the Import Your Own Data task type is flexible, including in the ways that you can provide the data needed for task verification. In this part of the course, we’ll explain the various data source options and what is required to set up each one. Scroll down to get started.
<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/046d56bb-337c-428c-ba45-93717675a29f/44746536-e16d-4400-be7a-0e61592d1c40/Round_Gradient_Background_(1).png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/046d56bb-337c-428c-ba45-93717675a29f/44746536-e16d-4400-be7a-0e61592d1c40/Round_Gradient_Background_(1).png" width="40px" />
Course Navigation
In short, to set up an Import Your Own Data task, you will need the data of who (what wallet address) has completed the task you wish to verify in your quest. There are several options for how to provide this data to Galxe, which are listed under the Credential Source section of the Import Your Own Data task set up screen.
Let’s look over the credential source options and explain each.
The first two Credential Source options that you will see in an Import Your Own Data task set up are CSV and Google Sheet. In either case, you will need to prepare a spreadsheet which contains the address data of who has done the task you wish to verify. This should be in the form of a simple spreadsheet — just one column with all the wallet addresses, one to each row, will work. The spreadsheet should also have any formatting cleared from the address data as Galxe’s system has difficulty reading addresses if the text is formatted (such as being bolded, with a non-default font, etc.).
Once the spreadsheet is prepared, you’ll be able to upload it directly to Galxe for CSV files. For Google Sheet, you will add the Galxe Spreadsheet Bot as a viewer on the sheet to provide the data to Galxe. The account information for the Galxe Spreadsheet Bot is available directly on the Import Your Own Data task set up screen.
Syncing data periodically when using spreadsheets as a credential source
An additional requirement when using a spreadsheet as your credential source is periodic manual syncing of your data. When you think about it, since you are setting up the Import Your Own Data task before your quest launches, the data included in your spreadsheet will only contain those wallet addresses which have done your task in the past. If you would also like your task to verify for those wallet addresses who perform the task after the quest starts, you will need to add them to your data point.
Either for CSV or Google Sheet, Galxe supports the ability to update your task’s data, either by re-uploading the CSV file or manually syncing the Google Sheet, even after your quest launches. In this case, it’s important to plan ahead and make sure that you or someone from your team will be able to update the data on a regular basis. If possible, Galxe recommends updating your task data daily when using a spreadsheet as your credential source, and to communicate your update schedule in your task description.
Galxe also supports querying GraphQL or REST API databases as a data point in Import Your Own Data tasks. The advantage of using such databases as your Credential Source is that the databases can update in real time with any new data of who has done your task, so there is no need to manually update the task completion data of after your quest launches (as was the case with using a spreadsheet as a credential source).
The main requirement of using database queries as your credential source is an endpoint URL. This URL represents the location where Galxe will direct its queries for task verification purposes. You can think of these queries as Galxe asking your endpoint, Has this wallet address done this task? **The endpoint then returns an answer of yes or no (1 or 0) based on the data it contains.
Exactly what is required to prepare your database’s endpoint for use in an Import Your Own Data task will vary from task to task, and depends on whether such an endpoint already exists and what methods your project already uses to track its onchain data. Often, developers will have a preference of which database type they would like to us. In Galxe’s experience, the most popular database type for onchain task verification is REST API.
Regardless of which database type you decide to use, you will want to share Galxe’s developer documentation with your dev and ask them to prepare the required info for your task. All of the required details are described in the documentation. What you might tell your dev is, I’m setting up an onchain task on Galxe and need a data source for the task verification. Your dev can read over the documentation which will guide them through proper setup of the endpoint. The dev can then write and provide you with what values you will need to input when you create the task on Galxe.
Here are the links to the developer documentation for each database type so that you can share the links with your dev:
.png){kind=link}