Skip to main content
POST
/
activities
{
  "type": "LINKEDIN",
  "subject": "[1/3] [FROM Acme Corp] John Smith",
  "body": "Hi Jane, I noticed your company is expanding...",
  "direction": "OUTBOUND",
  "ownerId": "user-123",
  "occurredAt": "2024-12-31T10:00:00Z",
  "contactId": "contact_8f3k2j",
  "companyId": "account_4k8j2m",
  "metadata": {
    "messageId": "linkedin-msg-123",
    "sequenceIndex": 1,
    "sequenceMessageCount": 3
  }
}

{
  "id": "activity-abc123",
  "type": "LINKEDIN",
  "subject": "[1/3] [FROM Acme Corp] John Smith",
  "direction": "OUTBOUND",
  "occurredAt": "2024-12-31T10:00:00Z"
}

Your Implementation Required

This endpoint must be implemented on your server
Enginy calls this endpoint to log conversation activity from campaigns including LinkedIn messages, emails, InMails, and connection requests.

​
Request

​
type
string
required
Activity type: EMAIL, LINKEDIN, LINKEDIN_CONNECTION, LINKEDIN_INMAIL
​
subject
string
Activity subject (formatted with sequence info and sender)
​
body
string
Message body content (may include HTML for emails)
​
direction
string
INBOUND (from contact) or OUTBOUND (from your team)
​
ownerId
string
Owner/sender user ID in your CRM
​
occurredAt
string
When the activity happened (ISO 8601)
​
contactId
string
Associated contact’s CRM ID
​
companyId
string
Associated company’s CRM ID
​
metadata
object
Additional metadata (messageId, sequenceIndex, sequenceMessageCount)
{
  "type": "LINKEDIN",
  "subject": "[1/3] [FROM Acme Corp] John Smith",
  "body": "Hi Jane, I noticed your company is expanding...",
  "direction": "OUTBOUND",
  "ownerId": "user-123",
  "occurredAt": "2024-12-31T10:00:00Z",
  "contactId": "contact_8f3k2j",
  "companyId": "account_4k8j2m",
  "metadata": {
    "messageId": "linkedin-msg-123",
    "sequenceIndex": 1,
    "sequenceMessageCount": 3
  }
}

​
Response

Return the created activity with at least an id field.
​
id
string
required
Unique identifier for the activity (required to prevent duplicates)
{
  "id": "activity-abc123",
  "type": "LINKEDIN",
  "subject": "[1/3] [FROM Acme Corp] John Smith",
  "direction": "OUTBOUND",
  "occurredAt": "2024-12-31T10:00:00Z"
}

​
Activity Types

TypeDescription
EMAILEmail messages sent/received
LINKEDINLinkedIn messages sent/received
LINKEDIN_INMAILLinkedIn InMail sent/received
LINKEDIN_CONNECTIONConnection requests sent/accepted

​
Subject Format

Enginy formats subjects to provide context: Outbound: [{index}/{total}] [FROM {Company}] {SenderName} 
[1/3] [FROM Acme Corp] John Smith
Inbound: [{ContactCompany}] {ContactName} 
[TechStartup Inc] Jane Doe
The id field is required in the response. Enginy stores this ID to prevent duplicate activity logs.