[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Assign message as case

> Assign a Smart Inbox message to a queue and a person as a case. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/sprout-social/assign_case

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Assign a Smart Inbox message to a queue and a person as a case.

Sprout Social API: https://cotlet.dev/docs/api/sprout-social.md

`POST https://cotlet.dev/api/v1/sprout-social/messages/{message_id}/case/assign`

Access: write. Confirm: waits for the user's OK before it runs.

Creates a case from the message with the queue, assignee and priority you give. Priority is Medium unless you set it. Tags and an internal comment are optional, and complete_message set to true also removes the message from the feed while keeping it in the assignee's Open Cases. The assignee gets an email and a notification with the case ID. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `message_id` | string | yes | Message ID from list_inbox_messages. |
| `queue` | string | no | Queue name from list_case_assignees. |
| `assignee` | string | no | User ID from list_case_assignees, or 'me'. |
| `priority` | string | no | Priority as the case form shows it. Medium by default. |
| `tags` | string[] | no | Tag names to put on the case. |
| `comment` | string | no | Internal comment for the assignee. |
| `complete_message` | boolean | no | Also mark the message complete. Default false. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/sprout-social/messages/msg_88a1f4/case/assign \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"queue":"Customer care","assignee":"u_204","priority":"Medium","tags":["Billing"],"comment":"Customer says they were charged twice in October."}'
```

**Python**

```python
result = client.call("sprout-social", "assign_case", {"message_id":"msg_88a1f4","queue":"Customer care","assignee":"u_204","priority":"Medium","tags":["Billing"],"comment":"Customer says they were charged twice in October."})
```

**Node.js**

```js
const result = await cotlet.call('sprout-social', 'assign_case', {"message_id":"msg_88a1f4","queue":"Customer care","assignee":"u_204","priority":"Medium","tags":["Billing"],"comment":"Customer says they were charged twice in October."});
```

**CLI**

```bash
cotlet call sprout-social assign_case --data '{"message_id":"msg_88a1f4","queue":"Customer care","assignee":"u_204","priority":"Medium","tags":["Billing"],"comment":"Customer says they were charged twice in October."}'
```

## Example response

```json
{
  "case_id": "case_1182",
  "message_id": "msg_88a1f4",
  "queue": "Customer care",
  "assignee": "u_204",
  "priority": "Medium",
  "tags": [
    "Billing"
  ],
  "comment": "Customer says they were charged twice in October.",
  "message_completed": false
}
```

Previous: [Complete message](https://cotlet.dev/docs/api/sprout-social/complete_message.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.