Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Actions26

Overview

This node integrates with the Pulse API to perform workflow actions related to various resources, including projects. Specifically, for the "Create Project" operation under the "Project" resource, it allows users to create a new project within an organization by providing essential details such as the project name, organizational unit, organization ID, and a JSON definition of the project.

This node is beneficial in scenarios where automated project creation is needed, such as:

  • Automatically setting up new projects when onboarding clients or teams.
  • Integrating project creation into larger workflows that manage organizational data.
  • Synchronizing project data from other systems into Pulse.

Example: A company uses this node to automatically create a new project in Pulse whenever a new client signs up on their platform, passing the client's organizational unit and project specifications dynamically.

Properties

Name Meaning
Name * The name of the project to be created.
Organizational Unit * The organizational unit under which the project will be categorized.
Organization ID * The identifier of the organization to which the project belongs.
Project Definition * The detailed project definition provided as a JSON string describing the project's setup.

Output

The node outputs a JSON object representing the newly created project as returned by the Pulse API. This typically includes all relevant project details such as its unique ID, name, organizational unit, status, and any other metadata defined by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active 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 API requests.
  • Proper permissions on the Pulse API are necessary to create projects within the specified organization.

Troubleshooting

  • Common Issues:

    • Missing required fields (e.g., project name, organizational unit, organization ID) will cause errors.
    • Invalid JSON format in the "Project Definition" property can lead to request failures.
    • Insufficient API permissions or invalid API credentials will result in authentication errors.
    • Network connectivity issues may prevent successful API calls.

  • Error Messages:

    • "The operation "createProject" is not supported for resource "projects"!" — indicates a misconfiguration of the operation or resource; ensure correct selection.
    • API error messages related to authorization or validation will be passed through; verify API key validity and input data correctness.

  • Resolution Tips:

    • Double-check all required inputs are provided and correctly formatted.
    • Validate the JSON structure of the project definition before execution.
    • Confirm API credentials are set up and have the necessary scopes.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch executions.

Links and References

Discussion