Create a Task
Put an item with the thread attached onto the workspace's Tasks list — the thing that survives the end of a shift, unlike an internal note.
Quick start
- Go to Automate → Workflows and open a workflow. Click + and pick Create a Task.
- Write a Task title, and optional notes for whoever picks it up — click Variable to insert a field.
- Choose an Owner (default: the conversation's assignee) and a Priority.
- Optional: set Due in (hours) to give the task a due time.
- Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
Watch out
- The owner is not notified — not when the task is created, and not if it becomes overdue.



Details
Getting here
Automate → Workflows, open a workflow, click + on the canvas, then pick Create a Task under Add Steps.
Before you start
- An owner, admin or agent can add this step and save the workflow. Publishing it is an owner or admin action.
- Building and running workflows depends on your plan; see pricing.
- Nothing outside Inchat has to be connected. The task appears on the Tasks page in the main menu.
Set up
- Open the workflow and click + where the task belongs.
- Pick Create a Task.
- Write the task title, and optionally notes for whoever picks it up — both can quote details from the run.
- Choose an owner, or leave it as Conversation's assignee (else shared queue), and a priority.
- Optional: set Due in (hours) to give the task a due time.
- Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.
Fields
- Task title
- The task's title, shown on the Tasks list. Click Variable next to the box to insert a field from the run, such as the contact's name.
- Limits: Truncated to 300 characters if longer. If it resolves to nothing at all, the step fails and no task is created.
- Task notes
- Optional notes for whoever picks the task up. Click Variable to insert a field from the run, the same way as Task title.
- Owner
- Who the task is assigned to, picked from a dropdown of current workspace members.
- Default: Conversation's assignee (else shared queue)
- Limits: Not re-checked against that list when the step later runs — see Limits.
- Priority
- Low, Normal or High.
- Default: Normal
- Due in (hours)
- Hours from now the task is due.
- Limits: Leave blank for no due date; zero or a negative number is treated the same as blank.
How it works
- The step creates one row on the workspace's Tasks list, carrying the title, notes, owner, priority, due time, and a link back to the conversation and its contact.
- The task also records which workflow created it, so an operator can trace why it exists.
- If no owner is named on the step, the task falls back to the conversation's current assignee; if there is none, the task is created unassigned — a real, supported state on the shared queue.
- If the conversation cannot be looked up when the step runs, the task is still created, just without its contact link and without the assignee fallback.
When it fails
- The title resolves to an empty string after quoting the run's fields: the step fails with the task title resolved to empty, and no task is created.
- The database write itself fails (for example, an owner id that does not exist at all): the step fails with could not create the task.
- You read the reason in the workflow's Activity tab: pick the run under Execution log and the step's line names it.
Limits
- If you name someone who has since left the workspace, the task is still created for them — this step does not check the workspace's member list the way Assign To (human) does.
- It does not notify the owner — no push, no in-app alert. The task simply appears on their Tasks list, or the shared queue if unassigned, next time they look.
- The workflow carries on to the next step either way — there is no separate Success or Failure branch.
- A due time is only a due time — nothing in this step alerts anyone when a task becomes overdue.
- Escalate can create its own follow-up task as a side effect, but only when the conversation already has an assignee.
- It also needs the AI agent's follow-up-task setting to be on, and nothing already summarising the current stretch of the conversation.
- An AI Reply step's own decline already does that, so Escalate right after one usually creates neither.
- Check the workflow's Activity tab to see whether Escalate's own task already ran, before adding this step for the same hand-off — otherwise you may end up with two.
Best practices
- Write the title and notes to quote the run — "Follow up with contact" tells nobody anything they did not already know; naming what was said or paid does.
- Use this step on the paths genuinely worth a person's time, and leave the rest of the workflow fully automated.
Use cases
- A high-value deal stage is reached, and a task is created for the account owner with the deal's value quoted in the notes.
- A path with no assignee yet routes to a team's queue and creates an unassigned task with a due time, so the follow-up is visible on the shared queue even before anyone claims the conversation.
FAQ and troubleshooting
- Does the person the task is assigned to get notified?
- No. The task appears on their Tasks list, but nothing pushes or alerts them when it is created.
- What happens if I leave the owner blank?
- It falls back to the conversation's current assignee. If the conversation has none, the task is created unassigned, on the shared queue.
Reading this with an AI assistant? Plain Markdown version.