Launchpad by Pegasystems icon

Launchpad by Pegasystems

Consume Pega Launchpad API

Actions22

Pulse → Add

AI-generated

Summary

Posts a new Pulse message on a Pega Launchpad case, optionally as a reply to an existing pulse message, via POST /dx/api/application/v2/messages.

Inputs

  • Authentication — Authentication method; only OAuth2 is offered (uses the pegalaunchpadOAuth2Api credential).
  • Base URL (required) — Base URL of the Pega Launchpad instance, e.g. https://your-pega-domain.com. A trailing slash is stripped.
  • Case ID (required) — ID of the case, sent as the message's context.
  • Message (required) — Text of the pulse message.
  • Additional Fields > Parent Message ID — ID of a parent pulse message to reply to. If omitted, an empty string is sent and the message is posted at the top level.

Output shape

One output item per input item. It contains the JSON body returned by the Pega API, plus a responseHeaders object holding the response headers.

The exact fields in the response body depend on the Pega API. If the response body is a string that isn't valid JSON, it is wrapped as rawBody. If a call fails, the node throws an error, or with Continue On Fail enabled, it outputs { error: message } for that item. Case ID, Message and Parent Message ID are read per item. Base URL is read once, from the first item.

Examples

Example 1: Post a status comment on a case after an upstream workflow step completes.

Case ID = {{$json.caseId}}, Message = 'Order processed successfully'. Leave Additional Fields empty.

Example 2: Reply to an existing pulse message within a thread.

Case ID = case ID, Message = reply text, Additional Fields > Parent Message ID = ID of the pulse message to reply to.

Links

Discussion