Creating custom quest tasks
Learn how to create custom validation tasks for your quests when built-in options don't meet your needs.
Overview
While Domino offers many built-in task types, your community might need specialized validation logic. Custom quest tasks let you define exactly how submissions are verified, giving you complete control over the user experience and validation criteria.
Understanding Task Types in Domino
Domino's quest system supports different types of tasks to engage your community.
Built-in Tasks
These are pre-configured tasks with standard validation:
Submit URL
Submit Text
Upload File
Tweet/Retweet/Reply
Quiz
Visit Link
And more

Task Templates
These are reusable tasks published to the task library, usually built on top of built-in tasks with custom validation logic.
Custom Tasks
When you need specific validation logic not covered by existing options, custom tasks give you complete control using Domino's automation system.
Custom tasks are perfect for:
Verifying complex user actions across multiple platforms
Creating unique interactive experiences
Implementing community-specific validation rules
Building verification logic that spans multiple steps
Creating Your First Custom Task
Adding a Custom Task to Your Quest
In your quest setup page, click Add Task
Select Custom from the task options
Give your task a descriptive name and add instructions in the description field
Setting Up Task Validation
Every custom task requires a validation automation that determines whether a user has successfully completed the task.
Navigate to the Validation tab in your task configuration
Click Create new to set up a validation automation
Building the Validation Automation
Automation Structure Requirements
A valid task automation must include:
A Task Submitted trigger that activates when a user attempts the task
A flow that evaluates the user's submission
A Task Completed action for successful validation
A Task Failed action for unsuccessful validation
Your automation must include both "Task Completed" and "Task Failed" actions, or users might get stuck when their submission doesn't meet your criteria.
Designing the Validation Logic
In the automation editor, start with the pre-configured Task Submitted trigger
Add conditions to evaluate the user's submission
Connect the conditions to either "Task Completed" or "Task Failed" endpoints
Crafting Conditional Logic
Use the conditional step to determine if the task should be marked as complete:
Click on the Set the task condition step
Configure your validation rules based on user input or external data
Make sure successful paths lead to "Task Completed" and failed paths to "Task Failed"
Configuring User Requirements
Required Accounts & Wallets
You can specify what connected accounts users need to complete your task:
Navigate to the User identification tab
Select which social accounts users need (Twitter, Discord, etc.)
Choose any wallet requirements for blockchain-related tasks

Advanced Configuration
Custom Input Fields
If your task requires user input beyond the built-in options:
Base your custom task on an appropriate built-in task (e.g., "Submit Text" for text input)
Configure the input fields in the Config tab
Access these inputs in your validation automation
Custom Success Messages
Configure what users see when they complete the task:
In your validation automation, use the Task Completed action
Add a custom success message in the "reason" field
Enable "Use success message as claim success message" to display this to users
Creating Reusable Task Templates
Once you've created a useful custom task, you can convert it to a template for reuse across multiple quests.
Converting a Task to a Template
Click the three dots menu (⋮) on your task card
Select Create task template
Confirm the conversion
Task templates can be reused across quests and optionally published to the Domino task library for anyone to use.
Testing Custom Tasks
Before publishing your quest:
Save your quest as a draft
Use the preview feature to test the task from a user's perspective
Verify that your automation correctly validates both successful and failed attempts
Troubleshooting
Common Custom Task Issues
Stuck in processing: Make sure your automation has both "Task Completed" and "Task Failed" endpoints
Validation not working: Check that your conditional logic correctly evaluates user submissions
Missing user input: Ensure you've configured appropriate input fields in the Config tab
Debugging Custom Task Automations
If your task validation isn't working as expected:
Test your automation directly in the automation editor
Check the automation runs for failed validations to understand what's happening
Verify that all connections between steps are correctly configured
Last updated