Overview
This node creates a new todo item in the EnlightenedMSP system. It is useful for automating task management workflows where todos need to be created programmatically based on input data or events within an n8n workflow. For example, you could use this node to automatically generate follow-up tasks when a support ticket is created or updated, ensuring that all necessary actions are tracked and assigned.
Properties
| Name | Meaning |
|---|---|
| Title | Title of the todo (required) |
| Description | Description of the todo |
| Due Date | Due date for the todo |
| Ticket Blocking | Whether this todo blocks the ticket (boolean true/false) |
| Autotask Ticket ID | ID of the associated Autotask ticket (number) |
| Is Onsite | Whether this todo requires onsite work (boolean true/false) |
| Estimated Minutes | Estimated time to complete in minutes (number) |
Output
The node outputs an array with one element per input item. Each output item contains a json field representing the newly created todo object as returned by the EnlightenedMSP API. The structure includes all details of the created todo, such as its title, description, due date, and other properties.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the EnlightenedMSP GraphQL API.
- The node uses a GraphQL client internally to communicate with the EnlightenedMSP endpoint.
- Proper configuration of the API endpoint URL and authentication credentials in n8n is necessary.
Troubleshooting
- Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Invalid or missing required properties (e.g., empty title) will result in errors from the API.
- Date formatting issues if the "Due Date" is not provided in a valid format.
- Error messages:
- Errors returned from the API will be thrown unless the node is set to continue on failure, in which case error details are included in the output JSON.
- To resolve errors, verify that all required fields are correctly filled and that the API credentials are valid and have sufficient permissions.
Links and References
- EnlightenedMSP API documentation (GraphQL): [Not provided in source]
- n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/
- General GraphQL usage guide: https://graphql.org/learn/