Actions7
Overview
This node integrates with the eKyte platform to create and retrieve various entities such as tasks, projects, tickets, boards, workspaces, notes, and notifications. Specifically, for the Create Task operation, it allows users to create a new task in eKyte by specifying detailed task attributes like title, type, workspace, priority, dates, estimated effort, and more.
Typical use cases include automating task creation from other systems or workflows, managing project tasks programmatically, or integrating eKyte task management into broader automation pipelines. For example, when a customer support ticket is created in another system, this node can automatically create a corresponding task in eKyte to track resolution steps.
Properties
| Name | Meaning |
|---|---|
| The user email associated with the eKyte operations; identifies the user performing the action. | |
| Titulo | The title of the task to be created. |
| ID Tipo Tarefa | Numeric identifier for the task type (task category/type ID). |
| ID Workspace | Numeric identifier of the workspace where the task will be created. |
| Prioridade | Priority group of the task, a number between 0 and 100 indicating urgency: 0 = Not prioritized, 1-25 = Low, 26-50 = Medium, 51-75 = High, 76-100 = Urgent. |
| Quantidade De Peças | Quantity related to the task (optional numeric value). |
| ID Projeto | Numeric identifier of the project associated with the task (optional). |
| Descrição | Description text providing additional details about the task (optional). |
| Iniciar Em | Start date and time of the task (required). |
| Concluir Até | Due date and time by which the task should be completed (required). |
| Esforço | Estimated time to complete the task, in minutes (required). |
| Tarefa Planejada | Boolean flag indicating whether the task is planned (true) or not (false). |
Output
The node outputs an array of JSON objects representing the response from the eKyte API after creating the task. Each output item contains the full JSON response from the API, which typically includes details of the newly created task such as its ID, status, timestamps, and any other metadata returned by eKyte.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential and a company identifier configured in n8n credentials to authenticate requests against the eKyte API.
- The node communicates with the eKyte REST API at
https://api.ekyte.com/n8n. - Proper network access to the eKyte API endpoint is necessary.
- The node enforces a minimum interval of 15 minutes between calls to the same operation to avoid rate limiting or API restrictions.
Troubleshooting
- Minimum Interval Error: If you receive an error stating that the minimum interval of 15 minutes between calls has not been respected, wait the specified number of seconds before retrying the operation.
- Authentication Errors: Ensure that the API key and company ID credentials are correctly set up and valid.
- Missing Required Fields: The operation requires certain fields such as user email, task title, task type ID, workspace ID, start and due dates, estimated time, and priority. Omitting these may cause errors.
- API Request Failures: Network issues or invalid parameters can cause the API request to fail. Check the error message returned by the node for details.
- JSON Parsing Issues: The node attempts to parse string responses as JSON; malformed responses could cause errors.
Links and References
- eKyte Official Website (general reference)
- eKyte API documentation (not publicly linked here; consult your eKyte account or support for API docs)
- n8n Documentation on Creating Custom Nodes