Skip to main content
Both events carry a crm_contact block, so you often do not need a second call to know who this person is in your CRM.

​
Fields

  • is_msg_sync_enabled: whether Groovin logs this conversation in your CRM. false when there is no CRM contact, null when unknown.
  • auto_create_outcome: the crm/contacts outcome when Groovin tried to create the contact.
  • matched_crm_contact_ids: only with ambiguous, up to 10. null otherwise.
  • crm_contact_id and crm_url: null for not_found, ambiguous and not_checked. crm_url is also null when Groovin cannot build a link to the record.
  • already_paired_in_groovin: null when it could not be read.

​
Fields that can be null or empty

Besides those above: groovin_user.email and name, linkedin_account.name, contact.name, contact.slug, contact.profile_url, contact.picture_url, message.subject, message.quoted, and, rarely, message.provider_id. message.text can be empty, but is never null. conversation_id and message.id are always text, but can be empty ("") in the rare case LinkedIn’s data lacks them. contact.linkedin_profile_id, slug, profile_url and is_crm_contact_creation_blocked are null when only a Sales Navigator profile id is known.