Read a lead's timeline
Everything that has happened with a lead in one feed: notes, tasks and recorded changes interleaved with the messages actually sent and received, newest first. Messages carry a channel of li or email. Open tasks are repeated in full under openTasks so a task due later still surfaces on the first page.
/leadActivities.getTimelineForLeadAuthorization
bearerAuth Enter your MailMoo API key (format: sk_live_...)
In: header
Query Parameters
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/leadActivities.getTimelineForLead?input=%7B%22leadId%22%3A%223c6e2b8e-0e8f-48db-8791-27271df10113%22%2C%22messageLimit%22%3A1%2C%22cursor%22%3A%22string%22%2C%22limit%22%3A30%7D"{ "items": [ { "kind": "activity", "sortAt": "string", "activity": { "id": "string", "leadId": "string", "workspaceId": "string", "userId": "string", "type": "NOTE", "content": "string", "metadata": {}, "dueAt": "string", "remindAt": "string", "scheduledFor": "string", "createdAt": "string", "updatedAt": "string", "property1": null, "property2": null }, "property1": null, "property2": null } ], "nextCursor": "string", "openTasks": [ { "id": "string", "leadId": "string", "workspaceId": "string", "userId": "string", "type": "NOTE", "content": "string", "metadata": {}, "dueAt": "string", "remindAt": "string", "scheduledFor": "string", "createdAt": "string", "updatedAt": "string", "property1": null, "property2": null } ], "sdrSenderName": "string", "leadRecipientLabel": "string", "property1": null, "property2": null}List pipeline stages GET
Returns every pipeline stage in the workspace, in board order. Stage names are workspace configuration, so fetch them here rather than hardcoding an ID: this is how you turn 'move the lead to Contacted' into the ID that pipeline updates expect.
Write a note on a lead POST
Adds a note to a lead's timeline. Notes are what you know about a lead that the data does not say, and they are visible to everyone in the workspace.