Actions26
- Activities Actions
- Project Actions
- Project Member Actions
- Project Document Actions
- Project Data Actions
- Project Work Unit Actions
- Project Indicators Actions
Overview
The node provides an integration with the Pulse API to manage project members within a project management context. Specifically, the Update Project Member operation allows users to modify details of an existing project member, such as their roles and managerial status.
This node is beneficial in scenarios where project team compositions change frequently, and automated workflows need to keep project member information up-to-date without manual intervention. For example, when a team member is promoted to a manager or assigned new responsibilities, this node can update their roles accordingly.
Practical examples:
- Automatically updating a project member's roles after HR updates.
- Changing a member’s managerial status based on project progress or organizational changes.
- Syncing project member data from an external system into Pulse via n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Member ID * | The unique identifier of the project member to update. |
| Actor Roles * | Comma-separated list of roles assigned to the member (e.g., agent_role,qc_role). |
| Is Manager | Boolean flag indicating whether the member has managerial privileges (true or false). |
* indicates required properties.
Output
The output is a JSON object representing the updated project member's data as returned by the Pulse API. This typically includes fields such as the member's ID, updated roles, managerial status, and possibly other metadata related to the project membership.
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 on the Pulse API side are necessary to update project member information.
Troubleshooting
Common issues:
- Invalid or missing Member ID: Ensure the Member ID provided corresponds to an existing project member.
- Incorrectly formatted Actor Roles: The roles must be provided as a comma-separated string matching valid role identifiers recognized by Pulse.
- Insufficient permissions: The API key used must have rights to update project members; otherwise, the API will reject the request.
Error messages:
"The operation "updateProjectMember" is not supported for resource "projectMembers"!": Indicates a misconfiguration in the operation or resource selection.- API errors related to authentication or authorization usually indicate invalid or expired credentials.
- Validation errors from the API may occur if required fields are missing or malformed.
To resolve these, verify input parameters, ensure correct API credentials, and confirm that the user has appropriate access rights.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- General best practices for managing project members in Pulse systems.