S.C.A.L.A. CRMInstall

Summary

Updates an existing ticket in S.C.A.L.A. CRM by sending a PUT request to /api/data/tickets/{id} with a JSON body of fields to change.

Inputs

• Record ID (required) — ID of the ticket to update. Read by the source as recordId and placed in the URL. The UI's property definition only shows it for the Data Table resource, so for Ticket Update the field may not appear in the UI. You may need to set it through an expression or JSON parameter.
• Record Data (required) — JSON object (recordData) holding the ticket fields to update. It is parsed with JSON.parse and sent as the request body. It defaults to '{}'. It is also declared only for the Data Table resource, so it may not appear in the UI for Ticket.

Output shape

One output item per input item. The API response is unwrapped: if it has a data or results array (or is itself an array), each element becomes a separate item. Otherwise the whole response object becomes one item.

The operation's filtered properties list is empty, so the UI shows no Ticket-specific parameters. The code still reads recordId and recordData. Invalid JSON in Record Data throws a parse error. Requests use Bearer token authentication with the scalaCrmApi credential (base URL and API token). The table name is fixed to 'tickets'.

Examples

Example 1: Close a ticket after a support workflow finishes

Resource: Ticket, Operation: Update. Set recordId to {{$json.ticketId}} and recordData to {"status":"closed"}. The field names must match the S.C.A.L.A. tickets schema.

Links

• n8n community nodes installation guide