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 workflow actions for managing activities within the Pulse API. Specifically, the "Unassign Member" operation under the "Activities" resource allows users to remove a member from an activity. This is useful in scenarios where team members need to be dynamically reassigned or removed from tasks or activities as project requirements evolve.
Practical examples include:
- Removing a user who is no longer responsible for a specific task.
- Updating activity assignments after team restructuring.
- Automating cleanup of activity memberships when a project phase ends.
Properties
| Name | Meaning |
|---|---|
| Activity ID * | The unique identifier of the activity from which a member will be unassigned. |
Output
The node outputs a JSON object representing the result of the unassignment operation. This typically includes confirmation details such as success status or updated activity information reflecting that the member has been unassigned.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Pulse API.
- The node depends on the Pulse API service being accessible and properly configured.
- No additional external dependencies are required beyond the API access.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Activity ID will cause the operation to fail.
- Insufficient permissions or invalid API credentials can lead to authentication errors.
- Network connectivity problems may prevent communication with the Pulse API.
Error messages:
"The operation "unassignMember" is not supported for resource "activities"!"— indicates a misconfiguration or unsupported operation; verify the selected operation.- Errors related to missing or invalid Activity ID — ensure the Activity ID is correctly provided and exists.
- Authentication errors — check that the API key credential is valid and has necessary permissions.
Resolving these usually involves verifying input parameters, ensuring correct API credentials, and confirming network connectivity.
Links and References
- Pulse API Documentation (for activities and membership management)
- n8n Documentation on creating custom nodes and using API credentials