VitePOS BridgeInstall

Summary

Sends a custom GET, POST, or PATCH request to any endpoint in the VitePOS Bridge (vtab/v1) or Analytics (vtpl/v1) WordPress REST namespaces, using the node's stored credentials. Use it for endpoints that have no dedicated operation.

Inputs

• API Namespace — Chooses the REST namespace: Bridge (vtab/v1, the default) or Analytics (vtpl/v1).
• Method — HTTP method: GET (default), POST, or PATCH.
• Endpoint (required) — Path inside the chosen namespace, e.g. /batches/status or /analytics/products/456. Defaults to /manifest. The request URL is built as /wp-json//. Leading slashes are normalized.
• Query JSON — JSON object sent as URL query-string parameters. Default {}. Invalid JSON raises an error.
• Body JSON — JSON object sent as the request body. Default {}. It is only sent when non-empty and the method is not GET. Invalid JSON raises an error.

Output shape

One output item per input item. Its json is the API's JSON response with an added human-readable response string.

For the raw resource the response text is a generic 'VitePOS Bridge request completed.' (or the API's message if the API returned status/success false). The API's own fields are spread alongside it. If the API response is not an object, or already has a response field, the payload is nested under raw. With Continue On Fail enabled, a failed item returns {error: message}. Otherwise the node throws. Each output item is paired to its input item.

Examples

Example 1: Fetch the bridge manifest

Namespace Bridge vtab/v1, Method GET, Endpoint /manifest, Query and Body left as {}.

Example 2: Query batch expiry status with custom parameters

Namespace Bridge, Method GET, Endpoint /batches/status, Query JSON {"near_days": 14, "available_only": 1}.

Example 3: Trigger the Woo dashboard sync

Namespace Analytics vtpl/v1, Method POST, Endpoint /analytics/sync-woo-dashboard, Query JSON {"range":"last_7_days"}.

Links

• n8n community nodes installation guide