Lemlist: Post Contacts Idoremail Notes

Add a note to a Lemlist contact by ID or email, also pushed to your connected CRM.

Tool ID: lemlist_post_contacts_idoremail_notes

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_post_contacts_idoremail_notes',
  {
    "idOrEmail": "jane.doe@example.com"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_post_contacts_idoremail_notes --input '{
  "idOrEmail": "jane.doe@example.com"
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "_id": "_123",
    "teamId": "team_123",
    "contactId": "contact_123"
  }
}

Use deepline describe lemlist_post_contacts_idoremail_notes --json for the latest machine-readable contract.

Input reference

Writes a note on a contact resolved by its id (ctc_xxx) or email, exactly as a note written in the lemlist app: it is stored as a note of the contact, pushed to your connected CRM (HubSpot, Salesforce, Pipedrive) like an in-app note, and logged in the team activity feed. The author is the user of the API key. The note is plain text, stored as sent, at most 10000 characters, and cannot contain a (the app’s guard against markup). A lone < is stored HTML-escaped as <, as in the app. A missing, empty or non-text note creates an empty note, as on POST /companies/{companyId}/notes.

Name	Type	Required	Default	Details
`payload.idOrEmail`	`string`	Yes	—	The unique identifier (`ctc_xxx`) or email of the contact
`payload.note`	`string`	No	—	The note content. Plain text, at most 10000 characters. A is refused, a lone `<` is stored as `<`. Maximum length: 10000.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	A text note attached to a contact record, as returned by `GET` and `POST /contacts/{idOrEmail}/notes`.
`result.data._id`	`string`	No	—	Unique note identifier (`act_xxx`)
`result.data.teamId`	`string`	No	—	Team ID that owns the contact
`result.data.contactId`	`string`	No	—	Parent contact ID (`ctc_xxx`)
`result.data.note`	`string`	No	—	Note text content
`result.data.userId`	`string`	No	—	ID of the user who wrote the note
`result.data.createdAt`	`string`	No	—	Creation timestamp Format: `date-time`.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation