Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Actions26

Overview

This node interacts with the Pulse API to perform workflow actions related to various resources, including Activities. Specifically, for the Activities resource and the Get List of Activities operation, it retrieves a paginated list of activities from the Pulse system. This is useful for scenarios where you want to fetch and process activity data such as task tracking, project updates, or team member assignments within an automation workflow.

Practical examples include:

  • Automatically retrieving recent activities to generate reports.
  • Syncing activity data with other tools like CRMs or project management software.
  • Filtering activities based on specific criteria to trigger further automation steps.

Properties

Name Meaning
Additional Fields A collection of optional parameters to customize the query:
- Sort Sort order of results, e.g., "created_at" for ascending or "-created_at" for descending order.
- Page Number The page number to retrieve in paginated results (default is 1).
- Page Size Number of results per page (default is 20).
- Filters One or more filters to narrow down results by specific fields. Each filter includes:
    Key The field name to filter on.
    Values Comma-separated list of values to match for the given key.
- Fields Specify which fields to include in the response for particular resource types. Each entry includes:
    Resource Type The resource type to specify fields for (e.g., "activities").
    Fields Comma-separated list of fields to include in the response.

Output

The node outputs JSON data representing the list of activities retrieved from the Pulse API. The structure typically includes an array of activity objects, each containing details such as activity ID, description, timestamps, assigned members, status, and other relevant metadata depending on the requested fields.

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

Dependencies

  • Requires 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 handle authentication and API requests.
  • No additional external services are required beyond the Pulse API access.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect filter keys or values may result in empty responses or errors.
    • Requesting unsupported fields or malformed pagination parameters can lead to API errors.

  • Error Messages:

    • "The operation "getActivityList" is not supported for resource "activities"!" — indicates a mismatch between selected resource and operation.
    • Network or authentication errors from the Pulse API will be returned as error messages in the output JSON if "Continue On Fail" is enabled.

  • Resolutions:

    • Verify that the API key credential is correctly set up and has necessary permissions.
    • Double-check filter keys and values against Pulse API documentation.
    • Ensure pagination parameters are positive integers.
    • Use the "Continue On Fail" option to handle errors gracefully during batch processing.

Links and References

Discussion