Fale JáInstall

Summary

Update a help center portal

Inputs

• apiType — Select which API to use based on your role and use case: application (agents/admins), client (end-users/customers), or platform (administrators, multiple accounts, platform-level configurations. Defaults to application scope if not specified. Determines the permission boundary and endpoint for the update request. Three options correspond to distinct Chapiary API namespaces within the Faleja node's Application, Client, and Platform modules respectively. Select based on your operational role and intended scope of changes.
• portalId (required) — The ID of the help center portal to update. Must be a valid numeric identifier existing within the selected API type's jurisdiction. If omitted or set to zero, the node will return a validation error preventing execution. This ID maps directly to the portal's unique identifier in the help center backend.
• updateFields — Fields to modify on the target help center portal. Accepts a collection of key-value pairs; each field is optional but at least one should be provided to constitute a meaningful update. Available fields: name (new title/name), description (new portal description), content (new portal content, primarily for article-type portals). Empty or missing values for a given key are ignored by the backend, allowing partial updates without overwriting unchanged attributes.

Output shape

object

The node returns the updated help center portal object reflecting the applied changes. Exact field composition depends on the API type and portal configuration. No additional side effects beyond the portal update are performed.

Examples

Example 1: Update portal name and description using the Application API

apiType: application, portalId: 42, updateFields: { name: 'New Portal Name', description: 'Updated portal description' }

Links

• n8n community nodes installation guide