Assign Task

Concept

Built-in Tasks is a concept feature. It's still being developed and can change before it's released. It's available only when the site's license includes the Concept feature Tasks.

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens, Workflows

Sets the assignee of a task. Only the Task administrators of the task's type and escalation workflows may assign tasks.

Typical Use Cases

• Give an unassigned purchase check to one buyer, from a page for the Task administrators
• Give a late task to a named person in an escalation step's workflow
• Take a task away from its assignee and give it to someone else

Don't use it to

• Take an unassigned task yourself. Use Assign Task to Current User instead.
• Hand on a task you're assigned. Use Delegate Task instead.
• Change the candidate roles, or give the task back to its roles. Use Reassign Task instead.

Related Actions

Action Name	Description
Reassign Task	Sets a new assignee, new candidate roles, or both.
Assign Task to Current User	The current user takes an unassigned task of their candidate roles.
Delegate Task	The assignee hands the task to another user.
Unassign Task	The assignee gives the task back to its candidate roles.

Input Parameter Reference

Parameter	Description	Supports Tokens	Default	Required
Task Id	The id of the task, usually a token such as [Task] in an escalation or event workflow, or [Id] in a grid row.	Yes	empty	Yes
User	The user to assign the task to: a user id, username or email.	Yes	empty	Yes
Comment	Why the task is assigned. The event workflows get it as [Comment]. It isn't saved on the task.	Yes	empty	No
Output Token Name	The name of a token, without brackets, that receives the task after the change, for example Task. See Task fields in tokens.	No	empty	No
On Error	Actions to run when the task can't be assigned. [ExceptionMessage] holds the reason. See Errors and refusals.	No	empty	No

Output

Token	Description
[<Output Token Name>]	The id of the task.
[<Output Token Name>:Assignee], [<Output Token Name>:Status] and the other fields	The task after the change. See Task fields in tokens.

Considerations

• Who may assign. The Task administrators of the task's type, superusers, and escalation steps' workflows, which act as the system. Others get Only a Task administrator of <type> can assign this task.
• Any user. The new assignee doesn't have to be a member of the task's candidate roles. The candidate roles stay as they are.
• What changes. Only the assignee. An In progress task stays In progress. If the task was delegated, it no longer shows who delegated it.
• The Assigned event. The workflow the type binds to Assigned runs with the reason assign, or reassign when the task already had an assignee, and with the previous assignee.

The action can fail with these messages, besides the ones in Errors and refusals:

Message	Why
Choose a user to assign the task to.	User is empty.
No user matches "<value>".	User is a username or email that matches no user.
User #<id> does not exist.	User is a user id that doesn't exist.
Only a Task administrator of <type> can assign this task.	The user running the action isn't a Task administrator of the type.

Examples

tip

To understand how to use the below examples, please see Running Examples.

1. Assign a task to the buyer picked in a form

Add this action to a button of a form for Task administrators. The form has a TaskId field with the task's id and a Buyer dropdown whose values are user ids. If the assignment is refused, the reason is shown under the form.

{
    "Title": "Assign Task",
    "ActionType": "PlantAnApp.Tasks.AssignTask",
    "Description": "Give the task to the chosen buyer",
    "Condition": null,
    "Parameters": {
        "TaskId": "[TaskId]",
        "User": "[Buyer]",
        "Comment": "Assigned by [User:DisplayName]",
        "OutputToken": "Task",
        "OnError": [
            {
                "Title": "Display Error Message",
                "ActionType": "ShowError",
                "Parameters": {
                    "Message": "<p>[ExceptionMessage]</p>"
                }
            }
        ]
    }
}

2. Give a late task to the head of purchasing

Add this action to a workflow that implements the Task Escalation contract and use it as an escalation step of the Purchase order type. [Task] holds the id of the late task. The workflow acts as the system, so it may assign the task.

{
    "Title": "Assign Task",
    "ActionType": "PlantAnApp.Tasks.AssignTask",
    "Description": "Give the late order to the head of purchasing",
    "Condition": null,
    "Parameters": {
        "TaskId": "[Task]",
        "User": "head.of.purchasing@example.com",
        "Comment": "Escalation step [Step]: the order wasn't placed in time.",
        "OnError": []
    }
}

Revised 11/12/2026