Actions11
- Deals Actions
- Contact Actions
- Emails Actions
- Organization Actions
- To-Dos Actions
Overview
This node integrates with the GrandCentral API to add a new To-do task within an automation workflow. It is designed to create tasks with specific details such as title, priority, due date, and assignment to a user. This functionality is useful for automating task management processes, ensuring that actionable items are created automatically based on triggers or other workflow conditions.
Practical examples include:
- Automatically creating follow-up tasks after receiving an important email.
- Generating To-do tasks when a deal reaches a certain stage in a sales pipeline.
- Assigning tasks to team members based on project updates or organizational changes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "Access Token" |
| Organization | (Optional) Identifier for the organization under which the To-do task will be created |
| Title | The title or name of the To-do task (required) |
| Details | Additional descriptive details about the To-do task (optional) |
| Priority | Priority level of the task; options: Low, Normal, High, Urgent (optional) |
| Due Date | Due date for the task in string format (optional) |
| Assigned To | Identifier of the user to whom the task is assigned (required) |
Output
The node outputs JSON data representing the response from the GrandCentral API after creating the To-do task. The output includes metadata about the execution item and the API response structured as an array of JSON objects. There is no binary data output.
Example structure of the output JSON might include fields such as task ID, status, creation timestamp, and any other relevant information returned by the API confirming the task creation.
Dependencies
- Requires an API key credential for authenticating requests to the GrandCentral API.
- The node makes HTTP POST requests to the
/automations/actionendpoint of the GrandCentral API. - No additional external dependencies beyond the configured API credentials and network access to the GrandCentral service.
Troubleshooting
- Authentication errors: Ensure the provided access token is valid and has sufficient permissions to create To-do tasks.
- Missing required fields: The node requires at least the "Title" and "Assigned To" properties. Omitting these will likely cause API errors.
- Invalid date formats: The "Due Date" should be provided in a format accepted by the API; otherwise, the request may fail.
- API request failures: Network issues or incorrect endpoint usage can cause errors. Verify connectivity and API endpoint correctness.
- Unexpected API responses: If the API returns errors or unexpected data, check the input parameters and consult the GrandCentral API documentation for correct usage.
Links and References
- GrandCentral API Documentation (general reference): https://grandcentral.example.com/api-docs (replace with actual URL)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/