360Messenger WhatsAppInstall

Summary

Sends a custom authenticated HTTP request (GET, POST, PUT or DELETE) to any endpoint under the 360Messenger v2 API and returns the parsed response. It is useful for API features the node has no dedicated operation for.

Inputs

• Method — HTTP method: GET, POST, PUT or DELETE. Defaults to POST.
• Endpoint — Path appended to https://api.360messenger.com/v2, for example /settings/webhook/set. A leading slash is added if missing. It is not marked required, but an empty value sends the request to the API base path.
• Body (JSON) — JSON request body, shown only for POST and PUT. Defaults to {}. A string is parsed as JSON, so invalid JSON causes an error.
• Query Parameters — Repeatable key/value pairs sent as the query string. Pairs with an empty key are skipped.

Output shape

One output item per input item, whose json is the API's response body. A string response is parsed as JSON, and an empty response becomes {}.

The request is sent with a Bearer token from the node's API key credential and a JSON content type. A GET or DELETE request sends no body. With Continue On Fail enabled, a failed item returns {error: message} instead of stopping the workflow. Each output item is paired with its input item.

Examples

Example 1: Set the account's webhook URL, which has no dedicated operation.

Method POST, Endpoint /settings/webhook/set, Body {"url":"https://example.com/hook"}

Example 2: Call a GET endpoint with query filters.

Method GET, Endpoint /some/endpoint, Query Parameters: key=limit, value=10

Links

• n8n community nodes installation guide