Actions22
- Agent Actions
- Assignment Actions
- Attachment Actions
- Case Actions
- Pulse Actions
- User Actions
Case → Get Attachments
AI-generatedSummary
Retrieves the list of attachments linked to a Pega Launchpad case by sending a GET request to /dx/api/application/v2/cases/{caseId}/attachments.
Inputs
- Authentication — Authentication method; only OAuth2 is available (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 whose attachments are listed. Inserted directly into the request path.
Output shape
One output item per input item. The item's JSON is the parsed API response body, with an added responseHeaders object holding the HTTP response headers.
The exact attachment fields depend on the Pega API response. This operation lists attachment metadata only and does not download file contents. If a non-JSON string body comes back, it is wrapped as rawBody. On error, the node throws a NodeApiError. If Continue On Fail is enabled, it returns an item with an error message instead.
Examples
Example 1: List all files attached to a case that was just created earlier in the workflow.
Resource: Case; Operation: Get Attachments; Base URL: https://myco.pegalaunchpad.com; Case ID: {{$json.ID}}
Example 2: Check whether a case has any attachments before sending a notification.
Case ID from an expression, followed by an IF node that tests the returned attachments list.