[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 follow-up tasks in Gladly

> Create a Gladly task for the right Inbox on every conversation that needs a follow-up, without duplicates. Runs daily, hosted, nothing to maintain.

Source: https://cotlet.dev/integrations/gladly-api-mcp-server/create-follow-up-tasks

A promise like "we will confirm the refund on Friday" is easy to lose in a Conversation Timeline, and a Task for the right Inbox is the only thing that brings it back.

Cotlet does it in your own Gladly account with list\_conversations, get\_conversation, get\_customer and create\_task, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=gladly) [All Gladly tools](https://cotlet.dev/integrations/gladly-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Gladly do this on its own?

Gladly Tasks can be created by hand in the Task Composer and through the REST API (checked 20 Oct 2026). Nothing in Gladly creates a Task from the content of a Conversation, and the API has no MCP server. A Task cannot be deleted once it exists, so duplicates are the main risk.

## How you do it in Gladly today

1. Find the Profile of the Customer, click the green plus icon and select Task.
2. In the Task Composer, type the details and invite colleagues to collaborate if needed.
3. Choose the Agent or Inbox that owns the Task and set the due date.
4. The owner finds the Task in My Customers, but only if the Task comes from an Inbox they are assigned to.
5. Gladly cannot delete a Task after it is created, so a duplicate stays on the timeline.

## How to create follow-up tasks in Gladly

Prompt

```
For every Open conversation tagged Refund Pending, create a task for the Billing inbox due on Friday: "Confirm refund went out". Skip customers who already have one.
```

1. 01  
### Find the Conversations  
list\_conversations with status open returns the queue, and get\_conversation shows the topics and the timeline of each one. The agent keeps only the Conversations that match your rule, such as the Refund Pending Topic.
2. 02  
### Check for an existing Task  
get\_customer returns the profile with its open Tasks. The agent skips a customer who already has a Task with the same text, because a Task cannot be deleted later.
3. 03  
### Pick the owner  
The Task goes to the Inbox or Agent you named. Tasks only reach people who are assigned to that Inbox, so the agent warns you when it names an Inbox with no Agents.
4. 04  
### Create the Task  
create\_task writes the text and the due date on the customer's timeline. It asks for your OK per call, because the owner is notified and the Task stays.
5. 05  
### Report the result  
The agent lists each customer, the owner and the due date, and the customers it skipped with the reason.

### What you get back

Example data

```
Open conversations tagged Refund Pending: 9
Tasks created 7, owner Billing inbox, due Fri 23 Oct
Skipped 2:
- Marco Silva: Task already open
- Ola Berg: Conversation closed this morning
```

### Other ways to ask

- Create a task for the Returns inbox on every conversation that mentions a damaged item.
- Show which customers would get a task, without creating anything.
- Every Monday, create a task for me on Open conversations older than 5 days.

## What Gladly allows, and what to know first

- Gladly Tasks cannot be deleted after they are created. The first Task can be edited, and comments on it can be deleted but not edited.
- A Task shows up in My Customers only when it comes from an Inbox the Agent is assigned to.
- Tasks assigned to an Inbox you are not in appear as updates in your Notifications Center.
- Gladly's Task Routing Window setting decides how soon before the due date a Task appears in the owner's list.
- A closed Task disappears from My Customers when no other Task is open, and it can be reopened.

create\_task asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Gladly Help: Create a Task](https://help.gladly.com/docs/create-a-task) · [Gladly Help: Find a Task](https://help.gladly.com/docs/find-a-task) · [Gladly Help: Close and Reopen a Task](https://help.gladly.com/docs/close-and-reopen-a-task) · [Gladly developer docs: REST API](https://developer.gladly.com/rest/)

## Call create\_task from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/gladly/customers/o2sg-TMTSD2rTwMuxzewbA/tasks \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Confirm refund went out","assignee_inbox_id":"vZgCEQlDR6aQz_0HeWZ9_Q","due_at":"2026-10-23T17:00:00Z"}'
```

Example response

```
{
"task_id": "pOVVdzweSumI4bFxjlT8LA",
"customer_id": "o2sg-TMTSD2rTwMuxzewbA",
"owner": "Billing inbox",
"due_at": "2026-10-23T17:00:00Z"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is gladly\_write → create\_task. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/gladly-api-mcp-server.md#automations)

## Gladly tools this automation uses

__Cotlet Gladly tools used to create follow-up tasks in Gladly__
| Tool | Parameters |
| ------------------- | --------------------------------------------------------------------- |
| list\_conversations | status, inbox\_id, cursor |
| get\_conversation | conversation\_id |
| get\_customer | customer\_id |
| create\_task | customer\_id, body, assignee\_inbox\_id, assignee\_agent\_id, due\_at |

[All 13 Gladly tools with descriptions](https://cotlet.dev/integrations/gladly-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Gladly to Cotlet?

Yes. You sign in to Gladly yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Gladly once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Gladly automations

- [Triage new Gladly conversations](https://cotlet.dev/integrations/gladly-api-mcp-server/triage-new-conversations.md)
- [Close resolved Gladly conversations](https://cotlet.dev/integrations/gladly-api-mcp-server/close-resolved-conversations.md)
- [Gladly API and MCP server: every tool](https://cotlet.dev/integrations/gladly-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Gladly.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Gladly.

[Sign up free](https://cotlet.dev/app/signup?app=gladly)

---

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.