S.C.A.L.A. CRM icon

S.C.A.L.A. CRM

Manage contacts, pipeline, tickets, and WhatsApp conversations in S.C.A.L.A. AI OS

Actions19

Ticket → Create

AI-generated

Summary

Creates a ticket in S.C.A.L.A. CRM by POSTing a JSON body to the /api/data/tickets endpoint of the configured instance.

Inputs

  • Record Data (recordData) — JSON object sent as the request body for the new ticket (default {}). The source reads this parameter for Ticket > Create, but the properties declare it only for the Data Table resource, so it may not appear in the UI for Ticket. If it is hidden, the node sends an empty body or the default value. Field names must match the S.C.A.L.A. tickets table schema, which the node doesn't define. Invalid JSON throws an error.
  • Credentials (scalaCrmApi) (required) — Supplies the base URL and API token. The token is sent as a Bearer Authorization header.

Output shape

The API response as workflow items. If the response (or its data or results property) is an array, each element becomes one item. Otherwise a single item holds the response JSON, typically the created ticket record.

No client-side validation of ticket fields is done. An empty body is sent as-is if the JSON is {}, because the body is only skipped when falsy. HTTP errors from the API cause the node to fail, as no continue-on-fail handling is implemented. The operation runs once per input item.

Examples

Example 1: Open a ticket when a support form is submitted

Resource: Ticket, Operation: Create, Record Data: {"subject": "{{$json.subject}}", "description": "{{$json.message}}", "priority": "high"}. Field names are examples and must match your tickets table.

Links

Discussion