---
title: "runs.attach"
method: POST
path: "/v1/runs/attach"
tags: ["runs"]
---

# runs.attach

`POST /v1/runs/attach`

## Request

- Base URL: `https://api.selda.ai`
- URL: `https://api.selda.ai/v1/runs/attach`
- Auth: HTTP bearer

Attach files to EVERY message in a campaign that has not gone out yet, by public https url or by storageId. Messages already sent keep exactly what they carried.

Dispatched to `runs.attach` on `POST /mcp/run`. This route is a different URL for the same call: the request is answered by the same dispatcher, with the same authentication, the same scope check, the same organisation scoping and the same refusals.

- Scope: `pipeline`
- A free sandbox key may call it
- MCP tools that wrap the same function: `selda_attach_files`
- Filled in from your API key, never sent by you: `orgId`

## Request body

- object
  - `leadId` string: A Convex document id in the `campaignRunLeads` table.
  - `runId` string: A Convex document id in the `campaignRuns` table.
  - `files` object[], required
    - `storageId` string: A Convex document id in the `_storage` table.
    - `url` string
    - `fileName` string
    - `filename` string
    - `mimeType` string
    - `contentType` string
    - `inline` boolean
    - `cid` string
    - `linksTo` string

## Response `200`

The call succeeded.

- object
  - `value` unknown, required
  - `request_id` string, required: Echoed in the `X-Request-Id` header.

## Other responses

- `400`: Unknown route, or arguments the validator refused.
- `401`: Missing, expired or revoked key.
- `403`: The key lacks the scope, the plan entitlement, or is a sandbox key on a live-only function.
- `429`: Rate limited. Wait for the next minute window and retry.
- `500`: The function threw. The message says what, without leaking internals.

---

[API](https://skmtc.dev/selda/apis/selda-api.md) · [All operations](https://skmtc.dev/selda/apis/selda-api/llms.txt) · [OpenAPI document](https://skmtc.dev/selda/apis/selda-api/revisions/f0b115a94c0f?raw)