Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Actions26

Overview

This node enables creating a new Project Work Unit within a specified project using the Pulse API. It is useful in scenarios where you want to programmatically add work units (tasks or subprojects) to an existing project for better task management and tracking.

Practical examples include:

  • Automatically creating work units when new projects are initiated.
  • Adding specific tasks or phases as work units based on external triggers or workflows.
  • Integrating with other systems to synchronize project work breakdown structures.

Properties

Name Meaning
Project ID * The unique identifier of the project under which the work unit will be created. This is required.
Name The name/title of the work unit being created. Optional but helps identify the work unit clearly.

Output

The node outputs JSON data representing the newly created Project Work Unit. This typically includes details such as the work unit's ID, name, status, creation timestamps, and any other metadata returned by the Pulse API related to the created work unit.

No binary data output is involved.

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 Project ID: The API call will fail if the provided project ID does not exist or is malformed.
    • Authentication errors: If the API key credential is invalid or expired, the request will be rejected.
    • Network connectivity problems may prevent successful API calls.

  • Error messages:

    • "The operation "createProjectWorkUnit" is not supported for resource "projectWorkUnits"!" — indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.
    • API error messages from Pulse API (e.g., unauthorized, bad request) will be passed through; verify credentials and input parameters.

  • Resolution tips:

    • Double-check the Project ID value.
    • Verify that the API key credential is valid and has necessary permissions.
    • Ensure network access to the Pulse API endpoint.
    • Use the node’s “Continue On Fail” option to handle errors gracefully during batch executions.

Links and References

Discussion