Peach icon

Peach

Interact with the Peach WhatsApp Platform API

Actions17

Broadcast → Archive

AI-generated

Summary

Archives a completed Peach broadcast by sending a PATCH request to the Peach API for the given broadcast ID.

Inputs

  • Broadcast ID (required) — Unique ID of the broadcast to archive. It is inserted into the request path /api/v1/broadcasts/{id}/archive.
  • Request Options — Optional node settings for the HTTP request: batching (items per batch and interval in ms), ignore SSL issues, proxy URL, and timeout in ms (default 10000).

Output shape

The JSON response from the Peach API for the archive request, returned as the node's output item. It is typically the updated broadcast record, but the source does not define the response body.

No request body is sent. Authentication uses the peachApi credential against https://app.trypeach.ai. The operation description says it is for completed broadcasts, but the node does no client-side status check, so the API decides whether other statuses are rejected. API errors surface as node errors.

Examples

Example 1: Archive a finished campaign after it has been sent

Resource: Broadcast, Operation: Archive, Broadcast ID: {{ $json.broadcastId }}

Example 2: Clean up many broadcasts from a list without hitting rate limits

Broadcast ID set from an expression on each incoming item; Request Options > Batching with 10 items per batch and 2000 ms interval

Links

Discussion