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 in the system. The Get operation retrieves detailed information about a specific task relation by its unique identifier (UUID). It supports fetching nested related objects up to two levels deep, allowing users to obtain comprehensive data about the task relation and its connected entities.

Typical use cases include:

  • Retrieving detailed metadata about how tasks are related to other entities such as people, companies, or opportunities.
  • Fetching hierarchical relationship data for reporting or automation workflows.
  • Integrating task relation details into broader business processes or dashboards.

Example: You have a task relation ID and want to fetch not only the relation itself but also the directly related objects and their relations (depth level 2) to understand the full context of the task's connections.

Properties

Name Meaning
Task Relation ID UUID string identifying the specific task relation to retrieve.
Depth Name or ID Level of nested related objects to include in the response:
- 0: Only the primary task relation.
- 1: Task relation plus its direct relations.
- 2: Task relation, its direct relations, and their relations.
Options can be selected from a list or specified dynamically via an expression.

Output

The output is a JSON object representing the requested task relation entity. Depending on the chosen depth, this JSON may include:

  • The primary task relation's properties.
  • Nested objects directly related to the task relation (if depth ≥ 1).
  • Further nested relations of those related objects (if depth = 2).

This structure allows users to access rich, hierarchical data about task relations and their context.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Dalil AI API.
  • An API key credential must be configured in n8n to authenticate requests.
  • The node uses internal helper functions to format and parse custom fields and to handle API requests.

Troubleshooting

  • Invalid Task Relation ID: If the provided UUID is incorrect or does not exist, the API will likely return an error. Verify the ID is correct.
  • Depth Parameter Issues: Providing an invalid depth value (not 0, 1, or 2) may cause unexpected results or errors. Use the provided options or valid expressions.
  • API Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Network or API Downtime: Temporary connectivity issues or API outages will cause request failures; retry later or check service status.
  • Unexpected API Response Structure: If the API changes, the node might throw errors parsing the response. Updating the node or checking API documentation may be necessary.

Links and References

Discussion