# 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

| Platform                 | What's tracked            | Description                                                       |
| ------------------------ | ------------------------- | ----------------------------------------------------------------- |
| **Zealy**                | Quest completion          | Reward users who complete specific quests in your Zealy community |
| **Galxe**                | Campaign participation    | Reward users who participate in your Galxe campaigns              |
| **Discord**              | Server/channel membership | Reward users who join your Discord server or a specific channel   |
| **X (Twitter) — Follow** | Follow activity           | Reward users who follow your project's account on X               |
| **X (Twitter) — Post**   | Post verification         | Reward users who post specific content on X                       |

### Quest Platforms (Zealy & Galxe)

Quest integrations work on a **completion basis** — each user who completes the specified quest or campaign earns a reward.

| Step                      | What happens                                                                                          |
| ------------------------- | ----------------------------------------------------------------------------------------------------- |
| **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) |

{% hint style="info" %}
Quest rewards are usually configured as **fixed payouts** (e.g., 100 points per quest completed) rather than proportional distribution.
{% endhint %}

### Discord

| Integration      | Verification                                                        | Typical reward        |
| ---------------- | ------------------------------------------------------------------- | --------------------- |
| **Join Server**  | Checks if the user has joined the specified Discord server          | Fixed reward per join |
| **Join Channel** | Checks if the user has joined a specific channel within your server | Fixed reward per join |

### X (Twitter) Integrations

| Integration       | Verification                                                            | Typical reward          |
| ----------------- | ----------------------------------------------------------------------- | ----------------------- |
| **Verify Follow** | Checks if the user follows the specified account via OAuth              | Fixed reward per follow |
| **Verify Post**   | User submits the URL of their post, Fuul verifies it meets the criteria | Fixed reward per post   |

### 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")


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fuul.xyz/core-concepts/trigger-integrations/quests-and-social.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.