Pulse Office Action icon

Pulse Office Action

Office actions from Pulse API

Actions17

Overview

This node integrates with the Pulse API to manage various office-related resources, including planning data. Specifically, the "Delete Planning" operation allows users to remove a planning entry identified by its unique ID. This is useful in scenarios where scheduled plans need to be canceled or cleaned up, such as removing outdated project timelines or employee shift plans.

Practical example: If a manager wants to delete a specific planning record for a team member due to changes in project scope, they can use this node operation by providing the planning ID to remove that entry from the system.

Properties

Name Meaning
Planning ID * The unique identifier of the planning entry to delete. This is a required string input.

Output

The output JSON contains the response from the Pulse API after attempting to delete the specified planning entry. Typically, this will include confirmation of deletion or relevant status information. The node does not output binary data for this operation.

Example output structure:

{
  "json": {
    // API response confirming deletion or error details
  }
}

Dependencies

  • Requires an active connection to the Pulse API via an API key credential.
  • The node depends on the Pulse API helper utilities bundled within the node's codebase.
  • Proper configuration of the API authentication credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Planning ID will likely result in an error from the API indicating the resource was not found.
    • Missing or incorrect API credentials will cause authentication failures.
    • Network connectivity problems may prevent communication with the Pulse API.

  • Error messages and resolutions:

    • "Unknown operation" errors indicate that the operation name provided does not match supported operations; ensure "deletePlanning" is selected.
    • API errors related to authorization suggest checking the API key credential setup.
    • Errors about missing parameters mean the required "Planning ID" was not supplied or is empty.

Links and References

Discussion