Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Actions23

Overview

This node interacts with the Pulse API to manage project members within a project management system. Specifically, the "List Project Members" operation retrieves a list of members associated with a project. This is useful for scenarios where you need to display, analyze, or process information about who is involved in a project.

Practical examples include:

  • Fetching all members assigned to a specific project to send notifications.
  • Generating reports on project team composition.
  • Synchronizing project member data with other systems.

Properties

Name Meaning
Include Related Resources Select related resources to include in the response. Options: Project (includes project details).
Additional Fields Collection of optional parameters to customize the list retrieval:
- Sort Sort order of results, e.g., "created_at" for ascending or "-created_at" for descending.
- Page Number The page number for paginated results (default is 1).
- Page Size Number of results per page (default is 20).
- Filters Filters to narrow down results by specific fields. Each filter has a key and comma-separated values.
- Fields Specify which fields to include in the response for particular resource types.

Output

The node outputs JSON data containing the list of project members retrieved from the Pulse API. The structure typically includes member details such as IDs, names, roles, and possibly related project information if requested via the "Include Related Resources" property.

If binary data were involved (not in this operation), it would be summarized accordingly, but this operation returns only JSON data.

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 environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Requesting unsupported operations or resources will throw errors.
    • Pagination parameters out of range may result in empty responses.
    • Improperly formatted filters or fields can cause API errors.

  • Error Messages:

    • "The operation \"getProjectMemberList\" is not supported for resource \"projectMembers\"!" indicates a mismatch between selected operation and resource.
    • Network or authentication errors will typically return messages related to failed API calls.

  • Resolutions:

    • Verify that the API key credential is correctly set up and valid.
    • Ensure the resource and operation selections match supported options.
    • Check pagination and filter inputs for correctness.
    • Review API limits and permissions if requests fail unexpectedly.

Links and References

Discussion