Stirling PDFInstall

Summary

Changes the role of an existing user in a Stirling PDF instance by sending the username, new role, and optional team ID as query parameters to the server's admin user API.

Inputs

• username (required) — Username of the existing account whose role should change. Sent as the username query parameter.
• role (required) — New role to assign, as free text (no options list is declared). Sent as the role query parameter. Use a role value your Stirling PDF server recognizes.
• teamId — Numeric ID of the team to associate with the user. Defaults to 0. Sent as the teamId query parameter.
• requestOptions — Optional HTTP settings: batching (items per batch and interval in ms), ignore SSL certificate issues, proxy URL, and timeout in ms (default 10000).

Output shape

The response from the Stirling PDF server for the role-change request, one result per input item.

The source pack contains only a stub of the class, so the exact response body is not visible. The request is declarative routing, so the output is whatever the server returns. Authentication and permissions are server-side; the caller needs admin rights.

Examples

Example 1: Promote a user to an admin role after approval in a workflow.

Resource: User, Operation: Change Role, Username: {{ $json.username }}, Role: ROLE_ADMIN

Example 2: Move a user to a different team while changing their role.

Username: jdoe, Role: ROLE_USER, Team Id: 2

Links

• n8n community nodes installation guide