PeachInstall

Summary

Uploads a media file to the Peach WhatsApp platform by POSTing to /api/v1/medias. The request body is built from data, filename and contentType parameters, which the node doesn't expose, so the Binary Property field may not feed the upload.

Inputs

• Binary Property (required) — Name of the binary property on the input item that holds the file to upload (default data). The source is declarative only and never reads this field, so the request body doesn't use it.
• Request Options — Optional node settings: Batching (items per batch, default 50, and interval in ms, default 1000), Ignore SSL Issues, Proxy URL, and Timeout in ms (default 10000).

Output shape

The JSON response from Peach's POST /api/v1/medias endpoint, one output item per input item. It is presumably the created media record, but the source doesn't define the response fields.

The node is declarative with no custom execute. The routing body references $parameter["data"], $parameter["filename"] and $parameter["contentType"], but no such properties are defined for this operation. These values are likely to resolve empty or undefined, and the binary property is never read, so the upload may fail or send an empty payload. Test before relying on it. Authentication uses the peachApi credential against https://app.trypeach.ai.

Examples

Example 1: Upload a file downloaded by an earlier HTTP Request node

Resource: Media, Operation: Upload, Binary Property: data. Defaults for Request Options. Verify that the request carries the file data, since the body parameters aren't mapped.

Links

• n8n community nodes installation guide