Follow up on stale Freshsales deals

1. An admin sets the limit per pipeline under Admin Settings > Deals & Pipelines > Pipelines: click the pencil icon, enter days in Deals go stale after, and click Save.
2. In the Deals module, a rep opens Open Deals, chooses Pipeline from the dropdown, clicks the three dots icon on a deal and picks Show only rotten Deals.
3. The rep opens each red deal, reads its page and decides whether it is dead, waiting on the customer or just forgotten.
4. For each deal worth saving, the rep goes to the Activities Dashboard, clicks Add task, types a title, picks a due date, and searches for the deal in Related to before clicking Save.
5. The red card is only a colour, and the help article describes no task or reminder that comes with it, so the list is easy to leave for next week.

List my rotten deals in the Sales pipeline. Skip any with an open task or activity in the last 7 days. For the rest, create a follow-up task for me and leave a note with the reason. Tell me which ones look dead.

1. 01

   Pull the rotten list

   Your agent reads one pipeline at a time with list_rotten_deals and follows next_cursor to the end. The staling age is set per pipeline, so the same age can mean a deal is late in one pipeline and on time in another. On the Free plan the call fails, because Freshsales has no rotten deals there.

2. 02

   Separate dead from quiet

   The age counts from the day a deal was created, not from its last activity, so a red deal can still be active. get_deal returns last_activity_date, and the agent skips deals with activity inside the window in your prompt.

3. 03

   Skip deals already chased

   list_tasks with deal_id and the open filter shows whether a task is already waiting on that deal. A deal with an open task is left alone, so a weekly run does not stack a second task on the first.

4. 04

   Create the task

   create_task goes on the deal, owned by you or the deal owner, with the reason in the title, such as the age and the last activity date. Freshsales sets times in 30-minute steps, so the due time ends in :00 or :30. A collaborator gets an email, so each task waits for your OK by default.

5. 05

   Mark the dead ones

   Deals with no activity for far longer than your window are not moved to Lost by this job. add_note leaves a one-line reason on the deal, and the agent lists those deals for you to close yourself.

Rotten deals in Sales pipeline: 6 (stale after 30 days)
Tasks created 3, e.g. Annual support plan, 11 days past the limit, last activity 02 Oct
Skipped 2 (open task already waiting)
Looks dead, left for you 1: Retail kiosk, no activity since 01 Sep

curl -X POST https://cotlet.dev/api/v1/freshsales/tasks \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"Follow up: Annual support plan (41 days old, last activity 02 Oct)","due":"2026-10-26T10:00:00","related_to_type":"Deal","related_to_id":7000388}'

{
  "task_id": 8800140,
  "title": "Follow up: Annual support plan (41 days old, last activity 02 Oct)",
  "due": "2026-10-26T10:00:00",
  "status": "open",
  "owner": "Dana Reyes",
  "related_to": {
    "type": "Deal",
    "id": 7000388,
    "name": "Annual support plan"
  },
  "collaborators": []
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is freshsales_write → create_task. Example data.

• Move Freshsales deals to Won or Lost with a reason
• Log call notes and the next step in Freshsales
• Freshsales API and MCP server: every tool
• All use cases