Dalil AI icon

Dalil AI

Consume Dalil AI API

Overview

This node integrates with the Dalil AI API to manage various CRM-related resources such as people, companies, notes, note relations, opportunities, pipelines, tasks, and their relations. Specifically, for the Note Relation resource with the Delete operation, it deletes a specified note relation by its unique identifier.

Use cases include automating the removal of associations between notes and other entities (like people or companies) in your CRM system. For example, if a note is no longer relevant to a particular contact or opportunity, this node can programmatically delete that link, keeping your data clean and up-to-date.

Properties

Name Meaning
Note Relation ID UUID string identifying the note relation to delete

The node expects the "Note Relation ID" property to specify which note relation to delete.

Output

The output JSON object after a successful delete operation contains:

  • success: A boolean indicating whether the deletion was successful (true).
  • id: The UUID string of the deleted note relation.

Example output:

{
  "success": true,
  "id": "uuid-of-deleted-note-relation"
}

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Dalil AI API.
  • Requires an API key credential configured in n8n for authentication with the Dalil AI service.
  • The node uses HTTP DELETE requests to the endpoint /rest/noteTargets/{noteTargetId} where {noteTargetId} is the Note Relation ID.

Troubleshooting

  • Invalid or missing Note Relation ID: Ensure the provided Note Relation ID is a valid UUID string corresponding to an existing note relation. An invalid ID will cause the API to return an error.
  • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions to delete note relations.
  • Network or connectivity issues: Confirm that the n8n instance can reach the Dalil AI API endpoints.
  • Unexpected API response structure: If the API changes, the node might throw errors related to unexpected responses. Updating the node or checking the API documentation may be necessary.

If the node is set to continue on failure, errors will be returned in the output JSON under an error field instead of stopping execution.

Links and References

Discussion