SmartCSRPro icon

SmartCSRPro

Create tickets and upsert contacts in SmartCSRPro

Create Ticket

AI-generated

Summary

Create a SmartCSRPro ticket for each incoming item, with a required subject and optional details, priority, assignee, due date, client, tags, category, and additional fields. The node sends a POST request to the tenant’s inbound-ticket webhook and returns the webhook response for each item.

Inputs

  • Subject (required) — Ticket title and main dashboard identifier.
  • Details — Optional Markdown body for the ticket’s Details section; supports headings, emphasis, lists, and links. Use \n for line breaks.
  • Priority — Ticket priority: Low, Normal (default), High, or Urgent.
  • Assigned To Name or ID — Team member to assign the ticket to; select from the loaded users or provide an ID by expression.
  • Due Date — Due date; the node sends only the first 10 characters of the value (YYYY-MM-DD).
  • Client Email — Client email, used to match or auto-create a contact record.
  • Tag Names or IDs — Optional ticket labels selected from the tenant’s tags or supplied as IDs by expression.
  • Category Name or ID — Optional category. If omitted and no form is selected, the category defaults to “Webhook to Ticket”; an explicit category overrides the selected form’s category.
  • Additional Fields: AMS ID — Client’s AMS applicant ID. The server matches by this ID before email and saves it to the matched or new contact; values containing square brackets are ignored server-side.
  • Additional Fields: Branch Name or ID — Branch to associate with the ticket; select a loaded branch or provide an ID by expression.
  • Additional Fields: Client Name — Client’s full name.
  • Additional Fields: Client Phone — Client’s phone number.
  • Additional Fields: External ID — External reference for idempotency; repeating the same value returns the existing ticket instead of creating a duplicate.
  • Additional Fields: Form Name or ID — Optional form. The ticket inherits the form’s category and title; an explicitly selected category overrides the form’s category.
  • Additional Fields: Include Link to Workflow — When enabled, appends a “Generated via n8n: View Workflow” link to the ticket details.
  • Additional Fields: Metadata — Free-form JSON stored on the submission, for debugging or reference.

Output shape

A list of items, each containing the webhook response as its JSON body.

One output item corresponds to each input item. If Continue On Fail is enabled, an item-level error object is returned for failed requests; otherwise the node throws an error.

Links

Discussion