[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)

# Create task

> Add a task with a type and due date on a lead, person, company or opportunity. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/copper-crm/create_task

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)

Add a task with a type and due date on a lead, person, company or opportunity.

Copper CRM API: https://cotlet.dev/docs/api/copper-crm.md

`POST https://cotlet.dev/api/v1/copper-crm/tasks`

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

Adds a task the way Add Task in the Related section does. activity_type is the Activity Type Copper asks for: Phone Call, Meeting, To-do (once turned on) or one of your custom types. Tasks are visible to the whole account by default, and an assignee other than you gets it in their list. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Task title. |
| `related_to_type` | enum | no | lead, person, company or opportunity. |
| `related_to_id` | string | no | Id of the record the task belongs to. |
| `due_date` | date | no | Due date, YYYY-MM-DD. |
| `activity_type` | string | no | Activity Type name, e.g. Phone Call or Meeting. |
| `assignee` | string | no | Name or email of the teammate. Default: you. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/copper-crm/tasks \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Follow up on Harbor Dental proposal: asked for revised pricing on Oct 6","related_to_type":"opportunity","related_to_id":"31844120","due_date":"2026-10-23","activity_type":"Phone Call"}'
```

**Python**

```python
result = client.call("copper-crm", "create_task", {"name":"Follow up on Harbor Dental proposal: asked for revised pricing on Oct 6","related_to_type":"opportunity","related_to_id":"31844120","due_date":"2026-10-23","activity_type":"Phone Call"})
```

**Node.js**

```js
const result = await cotlet.call('copper-crm', 'create_task', {"name":"Follow up on Harbor Dental proposal: asked for revised pricing on Oct 6","related_to_type":"opportunity","related_to_id":"31844120","due_date":"2026-10-23","activity_type":"Phone Call"});
```

**CLI**

```bash
cotlet call copper-crm create_task --data '{"name":"Follow up on Harbor Dental proposal: asked for revised pricing on Oct 6","related_to_type":"opportunity","related_to_id":"31844120","due_date":"2026-10-23","activity_type":"Phone Call"}'
```

## Example response

```json
{
  "task_id": "9061877",
  "name": "Follow up on Harbor Dental proposal: asked for revised pricing on Oct 6",
  "activity_type": "Phone Call",
  "due_date": "2026-10-23",
  "assignee": "Sam Ortiz",
  "related_to": {
    "type": "opportunity",
    "id": "31844120",
    "name": "Harbor Dental proposal"
  }
}
```

Previous: [Update opportunity](https://cotlet.dev/docs/api/copper-crm/update_opportunity.md)
Next: [Log activity](https://cotlet.dev/docs/api/copper-crm/log_activity.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.