Actions23
- Activities Actions
- Project Actions
- Project Member Actions
- Project Document Actions
- Project Data Actions
- Project Work Unit Actions
Overview
This node integrates with the Pulse API to manage project members within a project management system. Specifically, the "Add New Project Member" operation allows users to add a new member to a specified project by providing their account ID, the project ID, roles they will have in the project, and whether they should be designated as a manager.
Common scenarios where this node is beneficial include automating team setup when new projects are created, managing user permissions programmatically, or integrating project membership updates into broader workflows such as onboarding or resource allocation.
For example, after creating a new project, you can use this node to automatically add relevant team members with appropriate roles and managerial status without manual intervention.
Properties
Name | Meaning |
---|---|
Account ID * | The unique identifier of the user account to be added as a project member. |
Project ID * | The unique identifier of the project to which the member will be added. |
Actor Roles * | A comma-separated list of roles assigned to the member within the project (e.g., agent_role, qc_role). |
Is Manager | Boolean flag indicating whether the member should have manager privileges in the project. |
(* indicates required fields)
Output
The node outputs a JSON object representing the newly added project member's details as returned by the Pulse API. This typically includes confirmation of the member's association with the project, their roles, and managerial status.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Pulse API via an API key credential configured in n8n.
- The node depends on the Pulse API helper utilities bundled within the node's codebase to perform authenticated requests.
- Proper permissions for the API key are necessary to create or modify project members.
Troubleshooting
Common Issues:
- Invalid or missing
Account ID
orProject ID
will cause the operation to fail. - Incorrectly formatted
Actor Roles
(e.g., missing commas or invalid role names) may result in errors from the API. - Insufficient API permissions can lead to authorization errors.
- Invalid or missing
Error Messages:
"The operation "createProjectMember" is not supported for resource "projectMembers"!"
— This indicates a misconfiguration in the operation selection; ensure the correct operation is chosen.- API error messages related to invalid IDs or roles will be passed through; verify that all IDs exist and roles are valid.
- Network or authentication errors suggest checking API credentials and connectivity.
To resolve these issues, verify input values, ensure the API key has the necessary scopes, and confirm network access to the Pulse API endpoint.
Links and References
- Pulse API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General best practices for API Authentication