Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Overview

This node interacts with the Pulse API to manage project members within a project management workflow. Specifically, the "Remove Project Member" operation allows users to delete a member from a project by specifying the member's unique ID. This is useful in scenarios where team composition changes, such as when a member leaves a project or organization, and you need to update the project membership accordingly.

Practical examples include:

  • Automatically removing a user from all projects when they leave a company.
  • Cleaning up project memberships during project archival or restructuring.
  • Integrating with HR systems to sync project memberships based on employee status.

Properties

Name Meaning
Member ID * The unique identifier of the project member to be removed. This is a required string input.

Output

The node outputs a JSON object representing the result of the removal operation. Typically, this will confirm whether the deletion was successful or provide details about the removed member. If the operation fails, an error message will be included in the output JSON.

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 are needed on the Pulse API side to remove project members.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Member ID will cause the operation to fail.
    • Insufficient API permissions can lead to authorization errors.
    • Network connectivity problems may prevent communication with the Pulse API.
  • Error messages and resolutions:

    • "The operation "deleteProjectMember" is not supported for resource "projectMembers"!"
      This indicates a misconfiguration of the operation or resource; ensure the correct operation and resource are selected.
    • Errors containing "error" in the output JSON usually indicate API-level failures; verify the Member ID and API credentials.
    • If the node throws an error and continueOnFail is disabled, the workflow will stop; enabling continueOnFail allows processing subsequent items despite errors.

Links and References

Discussion