πQuests & Social
Fuul provides native integrations with quest platforms and social networks, allowing projects to reward users for community engagement and task completion without any custom development.
Supported Platforms
Zealy
Quest completion
Reward users who complete specific quests in your Zealy community
Galxe
Campaign participation
Reward users who participate in your Galxe campaigns
X (Twitter) β Follow
Follow activity
Reward users who follow your project's account on X
X (Twitter) β Post
Post activity
Reward users who post or engage with specific content on X
GitHub
Repository activity
Reward developers for contributions like starring repos, opening issues, or submitting PRs
Discord
Server activity
Reward users for joining and participating in your Discord server
Quest Platforms (Zealy & Galxe)
Quest integrations work on a completion basis β each user who completes the specified quest or campaign earns a reward.
1. Fetch participants
Fuul pulls the list of users who completed the quest/campaign from the platform's API
2. Deduplicate
New participants are identified by comparing against previously recorded completions
3. Record completion
Each new participant is recorded with a binary completion status
4. Distribute rewards
Rewards are distributed to all users who completed the quest (typically fixed rewards per completion)
Quest rewards are usually configured as fixed payouts (e.g., 100 points per quest completed) rather than proportional distribution.
Social Integrations (X, GitHub, Discord)
Social triggers verify that a user has performed a specific action on the platform. These are typically used in combination with other triggers to create multi-step campaigns (e.g., "Follow us on X and provide liquidity to earn bonus rewards").
X β Follow
Checks if the user follows the specified account
Fixed reward per follow
X β Post
Verifies the user posted or interacted with specific content
Fixed reward per post
GitHub
Tracks user activity on the specified repository
Fixed or variable per action
Discord
Verifies membership and activity in the server
Fixed reward for joining/participating
Why Use Native Integrations?
Unlike custom offchain events (which require API integration or CSV uploads), these native integrations are pre-built and require no development work:
Zero code β set up directly in the Fuul Incentives Manager
Automatic tracking β Fuul handles fetching and verifying participation
Deduplication β users are only rewarded once per quest or action
Combinable β mix with DeFi triggers for multi-action campaigns (e.g., "Complete quest + hold tokens")
Last updated