Actions26
- SQL Actions
- Client Access Actions
- User Access Actions
- Tools Actions
SQL → Get Client Token Policy
AI-generatedSummary
Retrieve the client token policy from Plug Database SQL resource, optionally specifying communication channel, input mode, and response formatting.
Inputs
- Channel — Select the communication method to execute the command, either REST or Socket.
- Input Mode — Choose between Guided mode for simplicity or Advanced mode to send a full JSON-RPC command.
- Response Mode — Determine how the Plug response is returned to n8n: Aggregated JSON, Chunk Items (for socket streams), or Raw JSON-RPC for debugging.
- Agent ID — Optional override to specify the target Plug agent; defaults to the credential's Default Agent ID if left empty.
- Client Token — Optional override for the Plug client token used; defaults to the credential's Default Client Token if empty.
- Include Plug Metadata — Boolean setting to include Plug metadata (__plug object) with channel, agent, request, and socket details in the output.
- Additional Options — Collection of optional parameters including Timeout (ms), API Version override, and custom RPC Meta JSON merged into the command.
- Socket Options — Settings for socket channel including maximum buffered rows, bytes, chunks, and stream pull window size (when Channel is set to Socket).
Output shape
a JSON object representing the client token policy data retrieved from the Plug SQL interface
The output format depends on the selected Response Mode: Aggregated JSON returns rows as items or a single JSON item, Chunk Items streams socket SQL outputs as chunks, and Raw JSON-RPC returns the full normalized JSON-RPC envelope. Metadata inclusion is controlled by the Include Plug Metadata option. The command supports overrides for Agent ID and Client Token parameters, and can operate over REST or Socket channels.