Pulse Office Action icon

Pulse Office Action

Office actions from Pulse API

Overview

The node enables interaction with an external Pulse API to manage office-related data. Specifically, for the "Announcement" resource and the "Create Announcement" operation, it allows users to create new announcements within their organization. This is useful in scenarios where automated workflows need to publish company-wide or department-specific announcements programmatically.

Practical examples include:

  • Automatically creating announcements about upcoming events or policy changes.
  • Scheduling announcements to be published on specific future dates.
  • Targeting announcements to particular organizational units such as departments or teams.

Properties

Name Meaning
Title * The title of the announcement. A required string that identifies the announcement.
Content (Markdown) The content of the announcement written in Markdown format. Supports rich text formatting.
Publishing Date * The date and time when the announcement will be published. Must not be before the current date.
Organizational Units * A comma-separated list of organizational units (e.g., departments) that the announcement targets.

Output

The node outputs a JSON object representing the created announcement. This typically includes details such as the announcement ID, title, content, publishing date, and targeted organizational units as returned by the Pulse API.

No binary data output is associated with this operation.

Dependencies

  • Requires connection to the Pulse API service via an API key credential configured in n8n.
  • The node depends on the Pulse API helper utilities bundled within the node's codebase to perform authenticated requests.
  • Proper configuration of the API authentication token or key is necessary for successful communication.

Troubleshooting

  • Common issues:

    • Providing a publishing date earlier than the current date may cause the API to reject the request.
    • Incorrectly formatted organizational units (e.g., missing commas) might lead to unexpected behavior or errors.
    • Missing required fields like title or content will result in validation errors.
  • Error messages:

    • "Unknown operation: "createAnnouncement" is not supported for resource "announcement"!" indicates a misconfiguration of the operation or resource parameters.
    • API authentication errors suggest invalid or missing API credentials; verify the API key setup.
    • Network or connectivity errors require checking the Pulse API endpoint accessibility.

Links and References

Discussion