> For the complete documentation index, see [llms.txt](https://docs.claimr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claimr.io/tasks/common-tasks/block-tasks.md).

# Block tasks

## What are Block tasks?

Block tasks are used to guide users through a simple action before they can continue — such as clicking a button or copying a piece of text. They don’t require any proof of completion, submissions, or account connections. Instead, Block tasks act as checkpoints in your quest, helping you control pacing, share static content, or confirm user interaction.

**Use Block tasks to**

* Prompt users to take a manual step (e.g., copy a code, follow an instruction)
* Add structural checkpoints between tasks
* Distribute static information without validation or tracking

## Configure a Block task

<figure><img src="/files/09YhAkpKe0R1JZslA0gr" alt="" width="563"><figcaption></figcaption></figure>

To configure a Block task in Claimr:

1. From your campaign dashboard, go to the **Quests** tab and click on the quest where you want to add a Block task.
2. On the quest settings page, click **+ Create new task**.
3. In the Category section, click **General**.
4. In the Groups section, click **Common**.
5. Select **Block** from the Tasks list.
6. Click **Continue**.

## Task settings

After selecting the task type, move to the next page and configure the following fields:

<figure><img src="/files/fjQU0losozt6UakgA6D7" alt="" width="563"><figcaption></figcaption></figure>

* **Completion points**: Set the number of points awarded when the user completes the task.
* **Points multiplier (%):** Add a percentage-based bonus to the total reward. For example, if your completion points are set to 100 and your multiplier is 5%, the final reward is 105 points.&#x20;
* **Recurrence:** Control how often users can complete the task:\
  Once – can only be completed one time per user.\
  Daily – available once every 24 hours.\
  Weekly – available once every 7 days.\
  Multiple – the task stays open and can be completed as many times as needed, one after another, without any waiting time.&#x20;

Now you can configure options specific to Block tasks.

* **Text to copy -** Add and customize the text that appears beside the button and can be copied to the clipboard. If left empty, only the button will be displayed.
* **Show button? -** Enable this toggle if you want users to confirm the action by clicking a button.&#x20;
* **Button text** – Customize the label shown on the confirmation button. Only appears if “Show button?” is enabled.

## How Block tasks appear to users<br>

<figure><img src="/files/ZOjZGlbSyGzYLzMJ2osS" alt="" width="367"><figcaption></figcaption></figure>

When users encounter a Block task, they see a simple interaction:

* Instructions and user's reward&#x20;
* The text to copy, displayed as a clickable link (if set)
* A button to confirm the action (if enabled)

Clicking the button completes the task and grants the configured reward.&#x20;

If recurrence is set as Multiple, the user can repeat the action right away — the task resets automatically after each completion.

{% hint style="info" %}
**Pro tip**: Use Block tasks as educational checkpoints or to share important information (like referral codes, wallet addresses, or instructions) that users need to copy before proceeding to the next step.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.claimr.io/tasks/common-tasks/block-tasks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.