> For the complete documentation index, see [llms.txt](https://docs.api.intratool.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.api.intratool.de/api-reference/automation/action-types/create-task-assignment.md).

# CreateTaskAssignment

Creates a new [`TaskAssignment`](/api-reference/tasks-2/task-assignments.md) when the [action](/api-reference/automation/actions.md) is executed.

## Type key

`createTaskAssignment`

## Config keys

| Key                                            | Type               | Required | Description                                                                                                                                            |
| ---------------------------------------------- | ------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `title`                                        | string             | yes      | Title of the created task assignment (supports [system variables](/introduction/system-variables.md)).                                                 |
| `description`                                  | string \| null     | no       | Description of the created task assignment (supports [system variables](/introduction/system-variables.md)).                                           |
| `task_template_id`                             | integer            | yes      | ID of the task template used for the created assignment.                                                                                               |
| `start_date_type`                              | string \| null     | no       | Strategy for resolving start date. Allowed values: `now`, `form_field_result`, `task_execution_ended_at`, `task_execution_for_execution_date`, `null`. |
| `start_date_type_form_field_id`                | integer \| null    | no       | Form field ID used by specific start-date strategies.                                                                                                  |
| `start_date_shift_interval`                    | string \| null     | no       | ISO 8601 duration string (`DateInterval` compatible) that shifts the resolved start date (e.g. `PT2H`, `P1D`) or `null`.                               |
| `executable_before_interval`                   | string \| null     | no       | ISO 8601 duration string (`DateInterval` compatible) used as execution window before start date (e.g. `PT30M`) or `null`.                              |
| `executable_after_interval`                    | string \| null     | no       | ISO 8601 duration string (`DateInterval` compatible) used as execution window after start date (e.g. `P1D`) or `null`.                                 |
| `show_before_interval`                         | string \| null     | no       | ISO 8601 duration string (`DateInterval` compatible) that defines how long before start date the assignment becomes visible (e.g. `PT15M`) or `null`.  |
| `computed_targetables_workflow_node_index`     | integer \| null    | no       | Workflow node index used by workflow-node targetable computation.                                                                                      |
| `computed_targetables_system_variable`         | string \| null     | no       | System variable key used for computed targetables.                                                                                                     |
| `computed_targetables_entity_select_field_ids` | integer\[] \| null | no       | Entity-select field IDs used for computed targetables.                                                                                                 |
| `exclude_executing_targetable`                 | boolean            | yes      | Excludes the currently executing user/department from targetables.                                                                                     |
| `user_confirmation_required`                   | boolean            | yes      | Whether assignees must explicitly confirm.                                                                                                             |
| `delayed_reason_required`                      | boolean            | yes      | Whether a delay reason is mandatory.                                                                                                                   |
| `deny_reason_required`                         | boolean            | yes      | Whether a deny reason is mandatory.                                                                                                                    |
| `reset_allowed`                                | boolean            | yes      | Whether resetting assignment execution is allowed.                                                                                                     |

## Example config

```json
{
  "title": "Follow-up",
  "description": "Please verify completion.",
  "task_template_id": 12,
  "start_date_type": "now",
  "start_date_shift_interval": "PT2H",
  "executable_before_interval": "PT30M",
  "executable_after_interval": "P1D",
  "show_before_interval": "PT15M",
  "exclude_executing_targetable": false,
  "user_confirmation_required": true,
  "delayed_reason_required": false,
  "deny_reason_required": false,
  "reset_allowed": true
}
```

## Available computed targetable types

All of [computed targetable types](/introduction/assignment-and-targeting.md) are available for `createTaskAssignment` Action type.


---

# 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:

```
GET https://docs.api.intratool.de/api-reference/automation/action-types/create-task-assignment.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.