Dalil AI icon

Dalil AI

Consume Dalil AI API

Overview

This node interacts with the Dalil AI API to manage "Task Relation" entities, which represent relationships or links between tasks and other objects (such as people, companies, opportunities, etc.) within the Dalil AI system. The Get Many operation retrieves multiple task relation records based on specified criteria.

Typical use cases include:

  • Fetching all relations linked to a specific task or set of tasks.
  • Retrieving task relations with sorting and filtering options for reporting or automation workflows.
  • Integrating task relation data into broader business processes or dashboards.

For example, you might use this node to get all task relations associated with a project’s tasks to analyze workload distribution or dependencies.

Properties

Name Meaning
Return All Boolean flag indicating whether to return all matching task relation records or limit the number of results returned.
Limit Maximum number of task relation records to return if "Return All" is false. Must be at least 1.
Options Additional options for the query:
- Order By String specifying how to sort the results. Format: "field1,field2[Direction]". Directions can be AscNullsFirst, AscNullsLast, DescNullsFirst, or DescNullsLast. Example: "createdAt,taskId[DescNullsLast]".

Output

The output is an array of JSON objects, each representing a task relation record retrieved from the Dalil AI API. Each object contains fields describing the relationship between a task and related entities (e.g., personId, companyId, opportunityId, petId, surveyResultId) along with any custom properties defined in the system.

If no records are found, the output will be an empty array.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Dalil AI API via an API key credential configured in n8n.
  • The node uses the Dalil AI REST API endpoints under /rest/taskTargets to perform the retrieval.
  • Proper permissions and API access rights are necessary to fetch task relation data.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect Order By syntax may result in API errors or unexpected sorting.
    • Requesting too many records without pagination or limits may lead to timeouts or rate limiting.
  • Error Messages:

    • "Unexpected API response structure" indicates the API returned data in an unexpected format; verify API version compatibility.
    • "Invalid property metadata" suggests that custom property definitions used in filters or options are malformed.
    • Network or permission errors typically manifest as HTTP 4xx or 5xx responses; check API key validity and user permissions.
  • Resolutions:

    • Ensure API credentials are correctly set up and have required scopes.
    • Validate Order By strings carefully against the documented format.
    • Use the "Limit" property to restrict the number of results when not returning all.
    • Handle errors gracefully using the node's "Continue On Fail" option if needed.

Links and References


Note: This summary is based solely on static analysis of the provided source code and input property definitions.

Discussion