> 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/custom-task.md).
# Custom task
## What are Custom tasks?
### What are Custom tasks?
Use Custom tasks to confirm that a user has completed an instruction that isn't directly trackable. These tasks let you define a required action (submitting a wallet address, pasting an ID, or entering a response) and optionally review it before approval. They're useful when you need flexibility, optional manual validation, or a free-form response.
**Use Custom tasks to:**
* Ask users to complete an off-platform action and paste proof
* Collect responses in a short or long text field
* Set up manual review with pending approval
* Add flexible steps between or after verified actions
For detailed information about general task settings, including task header, description, rewards, dependencies, and more, refer to [Task settings](/tasks/task-settings.md).
## Configure a Custom task
To configure a Custom task in claimr:
1. From your campaign dashboard, go to the **Quests** tab and click on the quest where you want to add a Custom 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 **Custom Task** from the Tasks list.
6. Click **Continue**.
## Task settings
After selecting the task type, move to the next page and configure the following fields:
* Completion points: The number of points awarded when the user completes the task.
* Points multiplier (%): Add a percentage-based bonus to the total reward. For example, a 20% multiplier increases the final reward by 20%.
* 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.
Now configure options specific to Custom tasks.
* Message – Add a short instruction that will appear above the input field. This can include context about what the user should submit (e.g., “Enter your email” or “Paste your transaction ID”).
* WIP Message – Add a message that will be shown while the task is pending approval. For example: “This task will be completed once your submission is reviewed.”
* Auto confirm? – Enable this toggle if you want the task to be automatically marked as complete once the user submits a response. If disabled, the task will stay in a “pending” state until manually approved.
* Long Text? – Enable this toggle to change the input field from a single line to a multi-line text area. Useful for collecting longer responses.
* Button text – Customize the label on the confirmation button (e.g., “Submit” or “Confirm”).
* Resubmit button text – Customize the label for the button that appears if the user is asked to submit again.
### How Custom tasks appear to users
When users encounter a Custom task, they see the following elements:
* The instruction you set in the Message field
* A single-line input or multi-line text box, depending on whether Long Text? is enabled
* A button to confirm the submission
If Auto confirm? is enabled, the task will be marked as complete immediately after the user clicks the button. If disabled, the task remains in a pending state until it is manually reviewed. The user will see the WIP Message during this period.
If recurrence is set as Multiple, users can repeat the action once it’s confirmed — with no cooldown between submissions.
{% hint style="info" %}
**Pro tip**: Custom tasks are perfect for collecting user-generated information like wallet addresses, social media handles, or completion confirmations for off-platform actions. Enable manual review when quality control is important.
{% 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/custom-task.md?ask=&goal=
```
`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.