Launchpad by Pegasystems icon

Launchpad by Pegasystems

Consume Pega Launchpad API

Actions22

Pulse → Reply

AI-generated

Summary

Posts a reply to an existing Pulse message on a Pega Launchpad case by sending a message with the given parent message ID to the case's context.

Inputs

  • authentication — Authentication method; only OAuth2 is available (uses the pegalaunchpadOAuth2Api credential).
  • baseUrl (required) — Base URL of the Pega Launchpad instance, without trailing slash (e.g. https://your-pega-domain.com). Read from the first item and used for all items.
  • caseId (required) — ID of the case (context) the Pulse conversation belongs to. Sent as context.
  • parentMessageId (required) — ID of the parent Pulse message being replied to.
  • message (required) — Text of the reply.

Output shape

One output item per input item, containing the JSON body returned by the Pega API for the created message, plus a responseHeaders object with the response headers.

The exact body fields depend on the Pega response. If the body is empty, the item contains only responseHeaders. With Continue On Fail enabled, a failed item outputs { error: <message> } instead of stopping the workflow.

Examples

Example 1: Reply to a Pulse message found earlier in the workflow

Resource: Pulse, Operation: Reply, Base URL: https://mycompany.pega.net, Case ID: {{$json.caseId}}, Parent Message ID: {{$json.pulseMessageId}}, Message: 'Thanks, we are looking into this.'

Example 2: Automated acknowledgement after fetching a case's Pulse feed

Use Pulse > Get to retrieve the feed, then Pulse > Reply with the Case ID and a message ID taken from the feed output, and a fixed or expression-based message.

Links

Discussion