Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Overview

This node interacts with a project management API to list members of a specific project. It is designed to retrieve detailed information about project members, optionally including related resources such as the associated project details. This functionality is useful in scenarios where you need to manage or analyze team composition, track member roles, or integrate project member data into workflows for reporting, notifications, or further processing.

For example, you might use this node to:

  • Fetch all members assigned to a project to send them updates.
  • Retrieve member lists filtered by certain criteria (e.g., role or status).
  • Include project details alongside member information for comprehensive context.

Properties

Name Meaning
Include Related Resources (included) Select related resources to include in the response. Options: Project (includes project details).
Additional Fields (additionalFields) Collection of optional parameters to customize the request:
- Sort: Sort order (e.g., "created_at" or "-created_at" for descending).
- Page Number: Page number for pagination.
- Page Size: Number of results per page.
- Filters: Filter results by specific fields using key-value pairs.
- Fields: Specify which fields to include in the response for particular resource types.

Output

The node outputs JSON data containing a list of project members matching the query parameters. The structure typically includes member details such as IDs, names, roles, and any included related resources like project information if requested.

If related resources are included, the output will contain nested objects representing those resources.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Pulse API service.
  • The node depends on the Pulse API helper utilities bundled within the node's codebase.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Requesting unsupported operations or resources will throw errors.
    • Pagination parameters set incorrectly may result in empty or incomplete data sets.
    • Filters with invalid keys or values may lead to no results or errors.
  • Error Messages:

    • "The operation "getProjectMemberList" is not supported for resource "projectMembers"!": Indicates a mismatch between selected resource and operation; verify correct selections.
    • Authentication errors usually mention invalid credentials or unauthorized access; ensure API key is valid and has required permissions.
    • Network or API errors may occur due to connectivity issues or API downtime; retry after some time.

Links and References

Discussion