> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Lemlist: Get Contacts Idoremail Notes

> Get Contact Notes. Lemlist Get Contacts Idoremail Notes reference includes SDK V2 and CLI requests, input constraints, response fields, and Deepline cost.

Get Contact Notes.

<Info>
  Tool ID: `lemlist_get_contacts_idoremail_notes`
</Info>

## Run this action

Use the TypeScript SDK for a single call. Put `ctx.tools.execute(...)` inside a Play when the call should be durable, scheduled, or run across a CSV.

```ts theme={null}
import { Deepline } from 'deepline';

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

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={null}
deepline tools execute lemlist_get_contacts_idoremail_notes --input '{
  "idOrEmail": "jane.doe@example.com"
}' --json
```

## Example response

The SDK exposes this shape at `result.toolResponse.raw`. Values below are representative.

```json theme={null}
{
  "data": {
    "data": [
      {
        "_id": "_123",
        "teamId": "team_123",
        "contactId": "contact_123"
      }
    ],
    "total": 123
  }
}
```

Use `deepline tools get lemlist_get_contacts_idoremail_notes --json` for the latest machine-readable contract.

## Input reference

Retrieves the notes attached to a contact, newest first by default. The contact is resolved by its id (`ctc_xxx`) or email within your team. Only notes are returned, not the contact's other activities. Use `page` and `limit` to paginate: the response carries the page in `data` and the number of notes in `total`; a contact without notes answers `200` with an empty `data`.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.idOrEmail` | `string` | Yes | — | The unique identifier (`ctc_xxx`) or email of the contact |
| `payload.limit` | `integer` | No | — | Number of notes per page. Default: 100. Maximum: 100. A missing, invalid or non-positive value falls back to 100. |
| `payload.page` | `integer` | No | — | Page number to retrieve, starting at 1. Default: 1. An invalid value falls back to 1; a page beyond the last one answers an empty `data`. |
| `payload.sortBy` | `"createdAt"` | No | — | The field to sort by. Only `createdAt` is supported; any other value is ignored. Allowed: `createdAt`. |
| `payload.sortOrder` | `"asc" \| "desc"` | No | — | The sort direction. Default: `desc` (newest first). Any other value sorts ascending. Allowed: `asc`, `desc`. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Retrieves the notes attached to a contact, newest first by default. The contact is resolved by its id (`ctc_xxx`) or email within your team. Only notes are returned, not the contact's other activities. Use `page` and `limit` to paginate: the response carries the page in `data` and the number of notes in `total`; a contact without notes answers `200` with an empty `data`.",
    "properties": {
      "idOrEmail": {
        "type": "string",
        "description": "The unique identifier (`ctc_xxx`) or email of the contact"
      },
      "limit": {
        "type": "integer",
        "description": "Number of notes per page. Default: 100. Maximum: 100. A missing, invalid or non-positive value falls back to 100."
      },
      "page": {
        "type": "integer",
        "description": "Page number to retrieve, starting at 1. Default: 1. An invalid value falls back to 1; a page beyond the last one answers an empty `data`."
      },
      "sortBy": {
        "type": "string",
        "description": "The field to sort by. Only `createdAt` is supported; any other value is ignored.",
        "enum": [
          "createdAt"
        ]
      },
      "sortOrder": {
        "type": "string",
        "description": "The sort direction. Default: `desc` (newest first). Any other value sorts ascending.",
        "enum": [
          "asc",
          "desc"
        ]
      }
    },
    "required": [
      "idOrEmail"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Provider response payload. |
| `result.data.data` | `array` | Yes | — | — |
| `result.data.data[]._id` | `string` | No | — | Unique note identifier (`act_xxx`) |
| `result.data.data[].teamId` | `string` | No | — | Team ID that owns the contact |
| `result.data.data[].contactId` | `string` | No | — | Parent contact ID (`ctc_xxx`) |
| `result.data.data[].note` | `string` | No | — | Note text content |
| `result.data.data[].userId` | `string` | No | — | ID of the user who wrote the note |
| `result.data.data[].createdAt` | `string` | No | — | Creation timestamp Format: `date-time`. |
| `result.data.total` | `integer` | Yes | — | Number of notes attached to the contact, across all pages |
| `result.meta` | `object` | No | — | Additional response metadata (status, paging). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Provider response payload.",
        "properties": {
          "data": {
            "type": "array",
            "items": {
              "type": "object",
              "description": "A text note attached to a contact record, as returned by `GET` and `POST /contacts/{idOrEmail}/notes`.",
              "properties": {
                "_id": {
                  "type": "string",
                  "description": "Unique note identifier (`act_xxx`)"
                },
                "teamId": {
                  "type": "string",
                  "description": "Team ID that owns the contact"
                },
                "contactId": {
                  "type": "string",
                  "description": "Parent contact ID (`ctc_xxx`)"
                },
                "note": {
                  "type": "string",
                  "description": "Note text content"
                },
                "userId": {
                  "type": "string",
                  "description": "ID of the user who wrote the note"
                },
                "createdAt": {
                  "type": "string",
                  "description": "Creation timestamp",
                  "format": "date-time"
                }
              },
              "additionalProperties": false
            }
          },
          "total": {
            "type": "integer",
            "description": "Number of notes attached to the contact, across all pages"
          }
        },
        "required": [
          "data",
          "total"
        ],
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

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

## Related documentation

* [Lemlist provider guide](/docs/providers/lemlist/guide)
* [SDK V2 quickstart](/docs/sdk-v2/quickstart)
* [SDK reference](/docs/sdk-v2/sdk-reference)
* [Run tools across a CSV](/docs/sdk-v2/batch-csv)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.