Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Overview

The node provides workflow actions for managing activities within the Pulse API. Specifically, the "Assign Member" operation under the "Activities" resource allows you to assign a member to a particular activity. This is useful in project management scenarios where tasks or activities need to be allocated to specific team members. For example, when a new task is created, this node can automatically assign it to a designated user and optionally start their work on it immediately.

Properties

Name Meaning
Activity ID * The unique identifier of the activity to which a member will be assigned.
Account ID * The account ID of the member who will be assigned to the activity.
Start Working Boolean flag indicating whether the assigned member should start working on the activity immediately after assignment.

Output

The output contains a JSON object representing the result of the assignment operation. This typically includes details confirming the member has been assigned to the specified activity, such as updated activity information or status confirmation. The node does not output binary 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 setup.

Troubleshooting

  • Common Issues:

    • Invalid or missing Activity ID or Account ID will cause the operation to fail.
    • Network connectivity issues or incorrect API credentials may prevent successful assignment.
    • Attempting to assign a member to a non-existent or inaccessible activity will result in errors.
  • Error Messages:

    • "The operation "assignMember" is not supported for resource "activities"!" — indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.
    • Errors related to authentication failures suggest checking the API key credential.
    • If the node returns an error message about missing parameters, verify that all required fields (Activity ID and Account ID) are provided.

Links and References

Discussion