{
"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"
}
Activities
Create activity
Log conversation activity (LinkedIn, email, etc.)
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
Request
string
required
Activity type:
EMAIL, LINKEDIN, LINKEDIN_CONNECTION, LINKEDIN_INMAILstring
Activity subject (formatted with sequence info and sender)
string
Message body content (may include HTML for emails)
string
INBOUND (from contact) or OUTBOUND (from your team)string
Owner/sender user ID in your CRM
string
When the activity happened (ISO 8601)
string
Associated contact’s CRM ID
string
Associated company’s CRM ID
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 anid field.
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
| Type | Description |
|---|---|
EMAIL | Email messages sent/received |
LINKEDIN | LinkedIn messages sent/received |
LINKEDIN_INMAIL | LinkedIn InMail sent/received |
LINKEDIN_CONNECTION | Connection requests sent/accepted |
Subject Format
Enginy formats subjects to provide context: Outbound:[{index}/{total}] [FROM {Company}] {SenderName}
[1/3] [FROM Acme Corp] John Smith
[{ContactCompany}] {ContactName}
[TechStartup Inc] Jane Doe
The
id field is required in the response. Enginy stores this ID to prevent duplicate activity logs.