{
"_id": "<string>",
"type": "<string>",
"title": "<string>",
"content": "<string>",
"text": "<string>",
"dueDate": "2023-11-07T05:31:56Z",
"userId": "<string>",
"leadId": "<string>",
"contactId": "<string>",
"campaignId": "<string>",
"sequenceId": "<string>",
"leadFirstName": "<string>",
"leadLastName": "<string>",
"leadCompanyName": "<string>",
"manual": true
}Task

Task screenshot from the lemlist app interface
A manual action assigned to a user to complete. Only the fields set on the task are returned.
Unique task identifier
Task type as stored, never null. Tasks created through the API use email, manual, phone, linkedinSend or whatsappMessage. Campaign tasks carry the type of their step (for example linkedinInvite, whatsappVoiceNote or sms), and reply and click tasks use opportunityReplied and opportunityClicked.
Task title
Task instruction, sent as message when the task is created or updated.
Text of the lead's LinkedIn reply, when it has one, on opportunityReplied tasks.
0 low, 1 medium, 2 high. Absent when the task has no priority.
0, 1, 2 Due date. Tasks carry no creation date.
ID of the assigned user, sent as assignedTo.
Associated lead ID
Associated contact ID
Campaign ID. A task on a lead carries the campaign of that lead.
Sequence ID
First name of the lead or contact
Last name of the lead or contact
Company name of the lead or contact. On a company task, the name (or domain) of the company, the only field that identifies it: the response carries no companyId.
true on tasks created by hand in lemlist or through the API, on campaign tasks whose step has its manual option on, and on out-of-office tasks. Absent otherwise, never false.
Was this page helpful?