---
title: "Link mail or WhatsApp messages to a task"
method: POST
path: "/api/v1/rest/attivita/tasks/{id}/messages"
tags: ["Activities"]
---

# Link mail or WhatsApp messages to a task

`POST /api/v1/rest/attivita/tasks/{id}/messages`

## Request

- Base URL: `https://api.custodo.ai`
- URL: `https://api.custodo.ai/api/v1/rest/attivita/tasks/{id}/messages`
- Auth: HTTP bearer

Links one or more messages — received or sent, mail or WhatsApp — to a task that already exists: the «Collega a un’attività» of the mail reader and of a WhatsApp chat. `channel` says whose ids they are: `email` (the default; ids from email_search, email_get or email_get_thread) or `whatsapp` (message ids from whatsapp_get_chat). The message stays where it is and is NOT filed in the Archivio; a mail that is already there brings its Archivio document along as an attachment. The member behind this credential must be able to open every message themselves — any other id answers not-found for the whole call — and edit the task (as attivita_update_task does). A task holds at most 50 linked messages. Idempotent: a message linked already is not linked twice, and `linked` counts only the new links. To start a NEW task from messages, a person does that from the mail reader or the chat.

## Path parameters

- `id` string, uuid, required

## Headers

- `X-Tenant-Id` string, uuid

## Request body

- object
  - `channel` 'email' | 'whatsapp': `email` (default) or `whatsapp`: which module the message ids belong to.
  - `message_ids` string[], required: Message ids — mail ones from email_search, email_get or email_get_thread; WhatsApp ones from whatsapp_get_chat.

## Response `200`

Done. `data` is the tool’s own answer.

- RestResult
  - `ok` true, required
  - `data` unknown, required

## Other responses

- `400`: The arguments did not validate: `error.message` names the field, what it expects and what arrived.
- `401`: No API key, or one that is malformed, unknown, revoked or expired.
- `403`: The call never ran: the module is off for this organisation, the credential lacks the permission or the module, the tier does not cover it, or the tool is destructive and the key was not minted for that.
- `404`: Nothing with that id in this organisation.
- `409`: The record is in a state that does not allow it — under legal hold, already sent, already closed. `error.code` says which.
- `422`: The tool ran and refused, in a sentence of its own (`TOOL_REFUSED`): the message says what to change. Retrying the same call will not help.
- `429`: The API key has spent its minute, or its day. Every request a key makes counts. See `Retry-After`.

---

[API](https://skmtc.dev/custodo/apis/custodo-integrazioni.md) · [All operations](https://skmtc.dev/custodo/apis/custodo-integrazioni/llms.txt) · [OpenAPI document](https://skmtc.dev/custodo/apis/custodo-integrazioni/revisions/16d336d3ec2a?raw)