Actions40
- Company Actions
- Note Actions
- Note Relation Actions
- Opportunity Actions
- Person Actions
- Pipeline Actions
- Task Actions
- Task Relation Actions
Overview
This node operation creates a relation linking a note to another record in the system, such as a person, company, or opportunity. It is useful when you want to associate notes with specific entities to maintain context and improve data organization.
Typical use cases include:
- Linking a note to a contact (person) to track communications or remarks.
- Associating a note with a company for account-related comments.
- Connecting a note to an opportunity to document deal-specific information.
For example, after creating a note about a client meeting, you can use this node to link that note to the relevant person and company records automatically.
Properties
| Name | Meaning |
|---|---|
| Note ID | UUID string of the note to link to a record (person, company, or opportunity). |
| Additional Fields | A collection of optional fields to specify the target record and custom properties: |
| - Company ID | UUID string of the company to link to the note. Leave empty if linking to person or opportunity. |
| - Person ID | UUID string of the person to link to the note. Leave empty if linking to company or opportunity. |
| - Opportunity ID | UUID string of the opportunity to link to the note. Leave empty if linking to person or company. |
| - Custom Properties | Additional custom fields specific to note relations. These depend on workspace configuration and can be multiple key-value pairs where each key is a custom property name or ID and the value is the property's value. |
Output
The output is a JSON object representing the created note relation record as returned by the API. This includes all standard and custom fields of the note relation, confirming the successful creation and providing details such as linked entity IDs and any custom properties set.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Dalil AI API service.
- An API authentication token credential must be configured in n8n to authorize requests.
- The node uses internal helper functions to format and process custom properties based on workspace metadata.
Troubleshooting
- Invalid Property Metadata Error: If a custom property specified does not match expected metadata, the node will throw an error indicating invalid property metadata. Ensure that custom property names or IDs are correct and available in your workspace configuration.
- API Request Failures: Network issues or incorrect API credentials may cause request failures. Verify API key validity and network connectivity.
- Missing Required Fields: The "Note ID" is mandatory. Omitting it will result in an error. Make sure to provide valid UUIDs for required fields.
- Custom Property Value Format: Custom property values must conform to their field types (e.g., dates in ISO format, booleans as true/false). Incorrect formats may cause errors.
Links and References
- Dalil AI API Documentation (hypothetical link)
- n8n Expressions Documentation - for dynamic property values
- Working with Custom Properties in Dalil AI (hypothetical link)