Dalil AI icon

Dalil AI

Consume Dalil AI API

Actions40

Overview

This node integrates with the Dalil AI API to manage various CRM-related resources, including people, companies, notes, tasks, opportunities, pipelines, and their relations. Specifically for the Person resource with the Get Many operation, it retrieves multiple person records from the Dalil AI system.

The node supports fetching either all person records or a limited subset, with options to filter, sort, and control the depth of related nested objects included in the response.

Common scenarios:

  • Synchronizing a list of contacts (people) from Dalil AI into another system.
  • Retrieving filtered or sorted lists of people based on specific criteria like name, score, or other custom fields.
  • Fetching detailed person data along with related entities (e.g., company, tasks) by specifying the depth level.

Practical example:

  • A user wants to get up to 100 people who have a score greater than 5, ordered by creation date descending, including their direct relations. They would set "Return All" to false, "Limit" to 100, and use the "Options" to specify filter as score[gt]:5, orderBy as createdAt[DescNullsLast], and depth as 1.

Properties

Name Meaning
Return All Boolean flag indicating whether to return all matching person records (true) or limit the number of results (false).
Limit Maximum number of person records to return when "Return All" is set to false. Minimum value is 1.
Options Collection of additional parameters to refine the query:
- Order By Sort results by one or more fields. Format: "field1,field2[Direction]". Directions can be AscNullsFirst, AscNullsLast, DescNullsFirst, DescNullsLast. Example: "createdAt,firstName[DescNullsLast]".
- Filter Filter results using field conditions. Format: "field[comparator]:value". Supported comparators include eq, neq, in, gt, gte, lt, lte, startsWith, like, ilike, is (for NULL/NOT_NULL). Example: "firstName[eq]:John,score[gt]:5".
- Depth Level of nested related objects to include in the response: 0 (only people), 1 (people + direct relations), 2 (people + relations + their relations). Can be selected from predefined options or specified via expression.

Output

The output consists of an array of JSON objects, each representing a person record retrieved from the Dalil AI API.

  • Each JSON object contains the full data of a person, including standard fields and any nested related objects depending on the specified depth.
  • If "Return All" is true, all matching records are returned; otherwise, only up to the specified limit.
  • The structure of each person object corresponds directly to the Dalil AI API's person entity schema.
  • No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Dalil AI API.
  • An API key credential for authenticating requests to Dalil AI must be configured in n8n.
  • The node uses HTTP methods (GET) to fetch data from endpoints like /rest/people.
  • Optional query parameters for filtering, sorting, pagination, and depth control are supported.

Troubleshooting

  • Common issues:

    • Invalid filter or orderBy syntax may cause API errors or empty results.
    • Requesting too large datasets without proper limits might lead to timeouts or rate limiting.
    • Incorrect depth values may result in incomplete or overly verbose responses.

  • Error messages:

    • "Unexpected API response structure" — indicates the API response did not match expected format; check API availability and credentials.
    • "Invalid property metadata" — usually occurs if custom properties are malformed; ensure custom property definitions are correct.
    • HTTP 4xx or 5xx errors — verify API key validity, permissions, and network connectivity.

  • Resolutions:

    • Validate filter and orderBy strings carefully according to documented formats.
    • Use "Return All" judiciously or apply reasonable limits.
    • Confirm that the API key credential is correctly set up and has necessary access rights.

Links and References

Discussion