Actions8
- Collaborators Actions
- OKRs Actions
- KPIs Actions
- Plans Actions
Overview
The Acelera node is designed to interact with the Acelera API, specifically for managing collaborators. In the context of the "Create" operation for the "Collaborators" resource, this node allows users to add new collaborators by providing essential details such as name, last name, email, and role ID. This functionality is beneficial in scenarios where teams need to manage user access and roles within a project or application efficiently. For example, a project manager can use this node to onboard new team members by creating their profiles directly through an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Name | The first name of the collaborator being created. |
| Last name | The last name of the collaborator being created. |
| The email address of the collaborator. This is required for notifications and account management. | |
| Role ID | The role assigned to the collaborator, which can be one of the following: User (1), Administrator (2), Only read (5). |
Output
The output of the execute() method will return a JSON object containing the response from the Acelera API after attempting to create a collaborator. This typically includes confirmation of the creation along with any relevant data about the newly created collaborator, such as their unique identifier and status. If the node can output binary data, it would generally represent files or images associated with the collaborator's profile.
Dependencies
- An API key credential is required for authentication with the Acelera API.
- The node relies on the Acelera API endpoint for creating collaborators, which must be accessible over the internet.
Troubleshooting
- Common Issues: Users may encounter issues related to invalid input data, such as missing required fields (name, last name, email) or incorrect role IDs.
- Error Messages:
- "Error en operación 'collaboratorCreate': [error message]" indicates that there was a problem during the API request. This could be due to network issues, invalid credentials, or server errors. To resolve this, check the input values and ensure that the Acelera API is reachable.
Links and References
- Acelera API Documentation (replace with actual link)
- n8n Documentation for further guidance on using custom nodes and workflows.