Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Actions26

Overview

This node allows you to manage project members within a Pulse project management system via its API. Specifically, the "Add New Project Member" operation lets you add a new member to a project by specifying their account ID, the project ID, roles they will have, and whether they are a manager. This is useful for automating team management tasks such as onboarding new collaborators or updating project teams dynamically.

Practical examples include:

  • Automatically adding a user to a project when they sign up or are assigned a task.
  • Setting specific roles for users in projects based on workflow conditions.
  • Marking certain members as managers to grant them elevated permissions.

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 * Comma-separated list of roles assigned to the member within the project (e.g., agent_role, qc_role).
Is Manager Boolean flag indicating if the member should have manager status within the project.

(* indicates required fields)

Output

The node outputs a JSON object representing the newly created project member. This typically includes details such as the member's ID, associated project ID, assigned roles, manager status, and possibly metadata returned from the Pulse API confirming the creation.

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 authenticated requests.
  • Proper permissions on the Pulse API side to create project members are necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Account ID or Project ID will cause the API call to fail.
    • Incorrectly formatted actor roles (not comma-separated) may result in errors or unexpected role assignments.
    • Lack of sufficient permissions in the API credentials can lead to authorization errors.

  • 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 errors related to invalid IDs or roles will usually be passed through; verify input values carefully.

  • Resolutions:

    • Double-check that all required properties are provided and correctly formatted.
    • Ensure the API key used has the necessary rights to modify project members.
    • Use the node’s "Continue On Fail" option to handle errors gracefully during batch operations.

Links and References

Discussion