Link notes to CRM entities (people, companies, opportunities) in Dalil AI — create, read, update, delete, and list noteTarget records that associate a note with one or more target records.

Dalil AI: Note Relation API Skills

Quick Reference

• Base URL: https://app.usedalil.ai

• Auth: Authorization: Bearer {apiKey}

• Content-Type: application/json (POST/PATCH requests only)

• Accept: application/json (GET requests)

• Resource path: /rest/noteTargets

Endpoints

No search operation available.

Create Note Relation

Link note to a person

{
  "noteId": "uuid-of-note",
  "personId": "uuid-of-person"
}

{
  "noteId": "uuid-of-note",
  "personId": "uuid-of-person"
}

{
  "noteId": "uuid-of-note",
  "personId": "uuid-of-person"
}

Link note to a company

{
  "noteId": "uuid-of-note",
  "companyId": "uuid-of-company"
}

{
  "noteId": "uuid-of-note",
  "companyId": "uuid-of-company"
}

{
  "noteId": "uuid-of-note",
  "companyId": "uuid-of-company"
}

Link note to an opportunity

{
  "noteId": "uuid-of-note",
  "opportunityId": "uuid-of-opportunity"
}

{
  "noteId": "uuid-of-note",
  "opportunityId": "uuid-of-opportunity"
}

{
  "noteId": "uuid-of-note",
  "opportunityId": "uuid-of-opportunity"
}

Fields

• noteId (UUID, required) — The note to link

• personId (UUID, optional) — Target person

• companyId (UUID, optional) — Target company

• opportunityId (UUID, optional) — Target opportunity

At least one target ID should be provided alongside noteId.

Update Note Relation

Updatable fields: noteId, personId, companyId, opportunityId

Get Note Relation

Default depth is 1 (includes linked note and target record).

List Note Relations

GET /rest/noteTargets?limit=60&order_by=createdAt[DescNullsLast]

GET /rest/noteTargets?limit=60&order_by=createdAt[DescNullsLast]

GET /rest/noteTargets?limit=60&order_by=createdAt[DescNullsLast]

Delete Note Relation

Deletes the link only, not the note itself.

Common Workflows

Create a note and link it to a person

Find all notes for a person

GET /rest/noteTargets?filter=personId[eq]

GET /rest/noteTargets?filter=personId[eq]

GET /rest/noteTargets?filter=personId[eq]

The response includes the full note object when depth >= 1.

Find all notes for a company

GET /rest/noteTargets?filter=companyId[eq]

GET /rest/noteTargets?filter=companyId[eq]

GET /rest/noteTargets?filter=companyId[eq]

Filter Examples

# Relations for a specific note
filter=noteId[eq]:note-uuid

# Relations linking to a person
filter=personId[eq]:person-uuid

# Relations where a person is linked (any person)
filter=personId[is]:NOT_NULL

# Relations where company is linked
filter=companyId[is]

# Relations for a specific note
filter=noteId[eq]:note-uuid

# Relations linking to a person
filter=personId[eq]:person-uuid

# Relations where a person is linked (any person)
filter=personId[is]:NOT_NULL

# Relations where company is linked
filter=companyId[is]

# Relations for a specific note
filter=noteId[eq]:note-uuid

# Relations linking to a person
filter=personId[eq]:person-uuid

# Relations where a person is linked (any person)
filter=personId[is]:NOT_NULL

# Relations where company is linked
filter=companyId[is]

Gotchas

1. No search operation — Note relations can only be filtered via the list endpoint.

2. Default depth is 1 — Unlike most entities (default 0), note relations default to depth 1 to include linked records.

3. Deleting a relation does not delete the note — Only the link is removed.

4. One target per relation — Each note relation links a note to ONE target. To link a note to both a person and a company, create two separate note relations.

5. URL-encode GET filter params — Filter strings contain special characters ([, ], :) that break manually constructed URLs. Use URL encoding when making requests (e.g., curl -G --data-urlencode "filter=...").