# Create a task

> Creates a task bound to a workflow. By default the task is placed in the workflow's initial state; passing `state` places it directly in that named state instead — an alternate entry point for starting a task mid-flow (e.g. 'a new recorte for an existing theme by id'), rather than re-submitting from the initial state and hoping a guard or similarity gate recognizes it. Entering the resulting state, initial or named, behaves identically: that state's `on_enter` automation fires and its `stalled_after` clock arms.

<Heading
  as={"h1"}
  className={"openapi__heading"}
  children={"Create a task"}
>
</Heading>

<MethodEndpoint
  method={"post"}
  path={"/api/v1/tasks"}
  context={"endpoint"}
>
  
</MethodEndpoint>

Creates a task bound to a workflow. By default the task is placed in the workflow's initial state; passing `state` places it directly in that named state instead — an alternate entry point for starting a task mid-flow (e.g. "a new recorte for an existing theme by id"), rather than re-submitting from the initial state and hoping a guard or similarity gate recognizes it. Entering the resulting state, initial or named, behaves identically: that state's `on_enter` automation fires and its `stalled_after` clock arms.

<Heading
  id={"request"}
  as={"h2"}
  className={"openapi-tabs__heading"}
>
  <Translate id="theme.openapi.request.title">Request</Translate>
</Heading>

<ParamsDetails>
  
</ParamsDetails>

<RequestSchema
  {...require("./create-task.RequestSchema.json")}
>
  
</RequestSchema>

<StatusCodes
  {...require("./create-task.StatusCodes.json")}
>
  
</StatusCodes>