{
"_id": "<string>",
"crm": "<string>",
"method": "<string>",
"label": "<string>",
"createdAt": "2023-11-07T05:31:56Z",
"doneAt": "2023-11-07T05:31:56Z",
"contactId": "<string>",
"companyId": "<string>",
"crmObjectId": "<string>",
"updatedFields": {},
"skippedFields": [
{
"field": "<string>",
"crmField": "<string>",
"crmFieldLabel": "<string>"
}
],
"error": {
"code": "<string>",
"statusCode": 123,
"message": "<string>",
"label": "<string>"
}
}CRM Log
One operation lemlist ran with the team's connected CRM for a contact or a company, as returned by GET /v2/crm/logs.
Name of the operation, e.g. contact_update. direction tells a lemlist write from the CRM change it mirrors. Known values: activity_create, activity_import, association_from_company, association_from_contact, association_remove, association_update, call_create, call_update, company_create, company_delete, company_merge, company_owner_update, company_restore, company_update, contact_create, contact_delete, contact_merge, contact_owner_update, contact_restore, contact_update, custom_activity_create, deal_create, email_message_create, event_create, experience_update, lead_status_update, linkedin_message_create, note_create, note_import, note_update, sms_message_create, task_complete, task_create, task_delete, task_import, task_update, whatsapp_message_create. An operation lemlist has not named yet keeps its own identifier: filter with category rather than on this value. contact_owner_update and company_owner_update name the older owner changes: lemlist now pushes an owner change as contact_update / company_update. To list them all, filter with field=ownerId&category=contact,company.
Was this page helpful?