Actions23
- Activities Actions
- Project Actions
- Project Member Actions
- Project Document Actions
- Project Data Actions
- Project Work Unit Actions
Overview
The node provides workflow actions related to "Activities" within the Pulse API ecosystem. Specifically, for the "Unassign Member" operation, it removes a member assignment from a specified activity. This is useful in project management scenarios where team members need to be dynamically assigned or unassigned from tasks or activities as project requirements evolve.
Practical examples include:
- Automatically unassigning a team member from an activity when their role changes.
- Removing a user from an activity after task completion or reassignment.
- Managing workload distribution by programmatically updating activity assignments.
Properties
Name | Meaning |
---|---|
Activity ID * | The unique identifier of the activity from which a member will be unassigned. |
*Note: The property is required.
Output
The node outputs JSON data representing the result of the unassignment operation. Typically, this JSON will confirm the success of the unassignment or provide details about the updated activity state. The exact structure depends on the Pulse API response but generally includes status and possibly the updated activity information.
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 with the node implementation to perform API calls.
- Proper permissions on the Pulse API are necessary to modify activity assignments.
Troubleshooting
Common issues:
- Invalid or missing Activity ID: Ensure the Activity ID provided exists and is correctly formatted.
- Insufficient permissions: The API key used must have rights to modify activity assignments.
- Network or API errors: Check connectivity and API service status.
Error messages:
"The operation "unassignMember" is not supported for resource "activities"!"
— indicates a misconfiguration or unsupported operation; verify the selected operation.- Errors returned from the API (e.g., unauthorized, not found) will be passed through; check the error message for specifics.
To resolve errors, verify input parameters, API credentials, and network connectivity. Use the node's "Continue On Fail" option to handle errors gracefully in workflows.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- General guidance on API Authentication in n8n