Actions40
- Company Actions
- Note Actions
- Note Relation Actions
- Opportunity Actions
- Person Actions
- Pipeline Actions
- Task Actions
- Task Relation Actions
Overview
This node integrates with the Dalil AI API to manage various CRM-related resources, including tasks. Specifically, for the Task resource and the Create operation, it allows users to create new tasks within their workspace. This is useful in scenarios where you want to automate task creation based on triggers or other workflow events, such as creating follow-up tasks after a meeting, assigning tasks to team members automatically, or scheduling reminders.
Practical examples:
- Automatically create a task titled "Call client" when a new lead is added.
- Create a task with a due date and assign it to a specific team member when a support ticket is received.
- Generate review tasks with detailed descriptions for document approval workflows.
Properties
| Name | Meaning |
|---|---|
| Title | The title of the task (e.g., "Complete project proposal", "Call client", "Review documents"). |
| Additional Fields | A collection of optional fields to further specify the task: |
| - Assignee Name or ID | UUID of the workspace member assigned to this task. Can be selected from a list or specified via expression. |
| - Body | Task content in plain text or markdown format. It will be formatted for rich text display. |
| - Due Date | When the task is due, in ISO 8601 datetime format (e.g., "2024-06-30T15:00:00Z"). |
| - Status Name or ID | Task status, with options: "TODO" (To do), "IN_PROGRESS" (In progress), "DONE" (Done). Selectable from a list or via expression. |
Output
The node outputs JSON data representing the created task object returned by the Dalil AI API. This includes all properties of the newly created task, such as its unique identifier, title, body content, assignee information, due date, status, and any other metadata provided by the API.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the task, but this node focuses on JSON task data only.
Dependencies
- Requires an API key credential for authenticating with the Dalil AI API.
- The node uses internal helper functions to format markdown text into a rich text blocknote format before sending.
- The node depends on the Dalil AI API endpoints for tasks (
/rest/tasks). - Proper configuration of the API credentials in n8n is necessary for successful requests.
Troubleshooting
- Invalid property metadata error: If custom properties are used incorrectly or malformed, the node throws errors indicating invalid property metadata. Ensure that custom properties are correctly defined and serialized.
- API request failures: Network issues or incorrect API credentials can cause request failures. Verify API key validity and network connectivity.
- Invalid date format: The due date must be in ISO 8601 format; otherwise, the API may reject the request.
- Assignee ID not found: Assigning a task to a non-existent or unauthorized user ID will result in an error. Use the provided load options to select valid workspace members.
- Markdown formatting issues: The body field accepts markdown, but improper markdown syntax might not render as expected in the UI.
Links and References
- Dalil AI API Documentation (hypothetical link as actual URL is not provided)
- n8n Expressions Documentation
- Markdown formatting guide for task bodies (referenced internally in the node)
This summary covers the static analysis of the execute() method logic for the Task resource's Create operation, focusing on input properties, output structure, dependencies, and common troubleshooting points.