SmartCSRPro icon

SmartCSRPro

Create tickets and upsert contacts in SmartCSRPro

Actions2

Upsert Contact

AI-generated

Summary

Create or update a contact in SmartCSRPro by matching on the required AMS applicant ID or falling back to email. Optionally include detailed contact information, assign a preferred or fallback AMS user, and add a co-applicant. Optionally include a workflow link in the output for downstream use.

Inputs

  • Applicant ID (required) — AMS applicant ID serving as the primary key to match an existing contact within the tenant.
  • First Name (required) — Contact's first name.
  • Last Name (required) — Contact's last name.
  • Email — Primary email of the contact, lowercased and deduplicated server-side; also used as a fallback match key if Applicant ID does not resolve.
  • Cell Phone — Primary cell phone number of the contact, deduplicated server-side.
  • Assigned AMS Username — Preferred assignee's AMS username matched against users.amsUsername on the SmartFlows side.
  • Assigned AMS Agent Full Name — Fallback assignee matched by case-insensitive full name "First Last" if Assigned AMS Username does not resolve.
  • Additional Fields — Optional extra contact details including account name, address lines, applicant type, city, CRM ID, customer since date, lead source and status, state, ZIP, and an option to include a workflow link in the node output (not persisted to contact).
  • Co-Applicant — Optional co-applicant information comprising first name, last name, email (also folded into the contact's email list for matching), cell phone (folded into phones list), and relationship to the primary applicant.

Output shape

a single JSON object representing the created or updated contact as returned by the SmartCSRPro API, optionally augmented with a workflowLink property if requested

The operation sends a POST request to the SmartCSRPro contacts webhook and returns the API response as JSON. If 'Include Link to Workflow' is enabled in Additional Fields, the output adds a 'workflowLink' URL pointing back to the current n8n workflow instance for use in downstream nodes such as Slack messaging.

Examples

Example 1: Upsert contact with required fields and basic optional data

Provide Applicant ID, First Name, Last Name, and optional Email and Cell Phone fields to either create or update the matching contact record.

Example 2: Upsert contact with co-applicant and additional fields

Provide primary contact details plus co-applicant info and additional fields like account name, address, lead source, and check 'Include Link to Workflow' to append a workflow URL to the output.

Links

Discussion