# CFM Workflow API V3 — Developer Guide

- **Applies to:** Sprinklr Customer Feedback Management (CFM) Workflow API V3 (`/api/v3/cfmWorkflow`)
- **V2 API reference:** [CFM Workflow API | Sprinklr Developer Portal](https://legacy-dev.sprinklr.com/cfm-workflow-api)


## 1. Overview

The **CFM Workflow API** starts a Customer Feedback Management workflow from an external system event. You supply a workflow identifier and a set of context parameters; Sprinklr runs the configured workflow, which can create or update a customer profile and trigger a personalized survey distribution over **Email, SMS, or WhatsApp**.

This turns real customer-journey moments — an online purchase, a form submission, an abandoned cart, a support-case closure — into a targeted, automated feedback request.

V3 exposes **two POST operations** under a single resource prefix:

| Operation | Method | Path | operationId |
|  --- | --- | --- | --- |
| Run workflow via event | `POST` | `/api/v3/cfmWorkflow/trigger` | `CfmWorkflowApiV3_triggerWorkflow` |
| Run workflow via event with profile details | `POST` | `/api/v3/cfmWorkflow/triggerWithNewProfile` | `CfmWorkflowApiV3_triggerWorkflowWithProfile` |


Both are tagged **CFM Workflow V3** in the OpenAPI specification.

The central design change from V2: **V2 documented a single endpoint** — `POST /api/v2/cfm-workflow/triggerWithNewProfile` — which always required a `unifiedProfile` object. V3 splits the capability in two, so a caller who only needs to fire an event against an already-known workflow context can use the lighter `/trigger` operation and omit profile construction entirely.

> **Prerequisite.** CFM must be enabled in your environment before you can use these APIs. Contact your Success Manager.


### 1.1 The workflow trigger data model

A trigger request is composed of at most three parts:

| Part | Field | Type | What it does | Present on |
|  --- | --- | --- | --- | --- |
| Workflow selector | `workflowId` | String | Identifies the active CFM workflow to execute | Both operations — **required** |
| Runtime context | `contextParams` | Object (map) | Free-form key/value pairs passed into the workflow, used by its conditions and actions | Both operations — optional |
| Customer identity | `unifiedProfile` | Object (`UnifiedProfile`) | A new or upserted customer profile the workflow acts on and distributes the survey to | `triggerWithNewProfile` only |


The workflow itself — its conditions, its branching, and the **Trigger Survey Distribution** action that actually sends the survey — is configured in the Sprinklr UI under **Sprinklr Insights → Customer Feedback Management → *survey* → Automation**, using the **CFM Workflow API** event type. The API only starts it. See [Setting Up a CFM Workflow API Event Workflow](https://www.sprinklr.com/help/articles/setting-workflow-trigger-events/setting-up-a-cfm-workflow-api-event-workflow/6807458589cac71a44d0022c) for the configuration side.

### 1.2 Where `workflowId` comes from

`workflowId` is the identifier of a workflow you have already created and activated in the CFM Automation canvas. It is a UUID-shaped string, for example `595b4041-6eba-400f-aff0-797f1029c6f2`.

You can obtain a ready-made request — with `workflowId` pre-filled from the current workflow — by opening the workflow record and choosing **Test API Connection**. That screen also lets you pick a **Channel Type** (Email, WhatsApp Business, SMS), supply a first name, full name, and social network user ID, and add extra `contextParams`, then click **Get API Request**. Copy the generated request, add your authentication headers, and run it. (Source: [Setting Up a CFM Workflow API Event Workflow](https://www.sprinklr.com/help/articles/setting-workflow-trigger-events/setting-up-a-cfm-workflow-api-event-workflow/6807458589cac71a44d0022c))

## 2. Base URLs and environments

**All production API calls are sent to:**

```
https://api3.sprinklr.com/{env}/api/v3
```

So the workflow resources in production are:

```
https://api3.sprinklr.com/{env}/api/v3/cfmWorkflow/trigger
https://api3.sprinklr.com/{env}/api/v3/cfmWorkflow/triggerWithNewProfile
```

Replace `{env}` with your assigned environment identifier (`prod0`, `prod2`, `prod3`, `prod4`, `prod5`, `prod6`, `prod8`, `prod11`, `prod12`, `prod15`, `prod16`, `prod17`, `prod18`, `prod19`, `prod21`, `prod24`, `production`, `spr-uat`, `azrqa` — see [APIs | Sprinklr Developer Portal](https://dev.sprinklr.com/apis) for the full environment list).

## 3. Authentication and common headers

All CFM Workflow API calls are authenticated with OAuth 2.0. See [API Overview](https://dev.sprinklr.com/api-overview) for portal registration, API key and secret generation, and the Authorize flow.

| Header | Value | Purpose | Required on |
|  --- | --- | --- | --- |
| `Authorization` | `{{accessToken}}` | Credential used by the API to authenticate a user with the server. For generating the authorization token, refer to the **Authorize** section on the developer portal. | All requests |
| `Key` | `{{apiKey}}` | API key that authenticates the application with the server. For generating an API key, refer to the **Getting Started** guide. | All requests |
| `Content-Type` | `application/json` | Determines the type of data (media/resource) present in the request body | Both `POST` operations |
| `Accept` | `application/json` | Determines the acceptable response type from the server | All requests |


**Permissions:** the CFM Workflow API event does not require any special permission within the Sprinklr Audience Profile Event module. However, you must configure the CFM Workflow API within your own systems and hold valid Sprinklr API authentication. (Source: [Setting Up a CFM Workflow API Event Workflow](https://www.sprinklr.com/help/articles/setting-workflow-trigger-events/setting-up-a-cfm-workflow-api-event-workflow/6807458589cac71a44d0022c))

## 4. Run workflow through event

Triggers an active CFM workflow using only a workflow identifier and runtime context. Use this when the customer profile the workflow acts on is already resolvable from the workflow's own configuration or from the supplied context, and you do not need to create or update a profile in the same call.

```
POST /api/v3/cfmWorkflow/trigger
```

- **operationId:** `CfmWorkflowApiV3_triggerWorkflow`
- **Summary (OpenAPI):** Run workflow via event
- **Request schema:** `CfmWorkflowTriggerV3Request`
- **Request body:** required
- **Response schema:** `APIResponse`


### 4.1 Request body

Schema `CfmWorkflowTriggerV3Request` — *Request body for triggering a CFM workflow via API v3.*

| Parameter | Sub-parameter | Type | Required | Description |
|  --- | --- | --- | --- | --- |
| `workflowId` | — | String | **Yes** | Unique identifier of the active workflow to be executed. |
| `contextParams` | — | Object | No | Contains contextual parameters passed to the workflow at runtime. Declared in OpenAPI as an object with `additionalProperties: {type: string}`. |
| `contextParams` | `IGNORE_DEDUP` | Boolean | No | Determines whether duplicate detection is ignored during workflow execution. |
| `contextParams` | `lang` | String | No | Language code used to localize workflow behavior or content. |
| `contextParams` | `country` | String | No | Country name used as contextual input for the workflow. |
| `contextParams` | `countryCode` | String | No | Two-letter country code associated with the specified country. |
| `contextParams` | `surveyFilled` | String | No | Indicates whether the survey has been completed. |


`workflowId` is the only field in the OpenAPI `required` array.

`IGNORE_DEDUP`, `lang`, `country`, `countryCode`, and `surveyFilled` are the keys shown in every supplied example. They are **conventional keys, not a closed enum** — `contextParams` is an open map, so you can pass any key your workflow's conditions reference.

### 4.2 Example request

```bash
curl --request POST \
  --url 'https://api3.sprinklr.com/{env}/api/v3/cfmWorkflow/trigger' \
  --header 'Authorization: {{accessToken}}' \
  --header 'Key: {{apiKey}}' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json' \
  --data '{
    "workflowId": "595b4041-6eba-400f-aff0-797f1029c6f2",
    "contextParams": {
      "IGNORE_DEDUP": true,
      "lang": "ar",
      "country": "Jordan",
      "countryCode": "SA",
      "surveyFilled": "true"
    }
  }'
```

### 4.3 Example response

```json
{
  "data": "Success",
  "errors": []
}
```

### 4.4 Response parameters

| Parameter | Type | Description |
|  --- | --- | --- |
| `data` | String | Indicates the outcome of the API request. `"Success"` when the workflow was triggered. |
| `errors` | Array[`Error`] | Contains any errors encountered during the request. Empty when no errors occurred. |
| `metadata` | Object (`ResponseMetadata`) | Response metadata. Declared on the `APIResponse` envelope but **absent from every supplied example** for this endpoint. |


## 5. Run workflow via event with profile details

Triggers an active CFM workflow and supplies a **new unified customer profile** in the same request. Sprinklr creates or updates the profile from the payload and then runs the workflow against it — which is what lets the workflow's **Trigger Survey Distribution** action reach a customer the platform has never seen before.

```
POST /api/v3/cfmWorkflow/triggerWithNewProfile
```

- **operationId:** `CfmWorkflowApiV3_triggerWorkflowWithProfile`
- **Summary (OpenAPI):** Run workflow via event with profile details
- **Request schema:** `CfmWorkflowTriggerProfileV3Request`
- **Request body:** required
- **Response schema:** `APIResponse`


This is the direct V3 successor to the single V2 endpoint `POST /api/v2/cfm-workflow/triggerWithNewProfile`.

### 5.1 Request body

Schema `CfmWorkflowTriggerProfileV3Request` — *Request body for triggering a CFM workflow with a new profile via API v3.*

| Parameter | Sub-parameter | Type | Required | Description |
|  --- | --- | --- | --- | --- |
| `workflowId` | — | String | **Yes** | Unique identifier of the active workflow to be executed. |
| `contextParams` | — | Object | No | Contextual parameters passed to the workflow at runtime. |
| `unifiedProfile` | — | Object (`UnifiedProfile`) | No | Unified profile of the new user. |


`workflowId` is the only field in the OpenAPI `required` array.

### 5.2 The `unifiedProfile` object

`unifiedProfile` is the platform-wide **`UnifiedProfile`** schema — *"Unified view of a profile in sprinklr."* It is the same object the Profile V3 API returns, and it is large. Only a small subset is relevant to a workflow trigger.

**Fields used in practice** (per every supplied example):

| Parameter | Sub-parameter | Type | Required | Description |
|  --- | --- | --- | --- | --- |
| `unifiedProfile` | `id` | String | No | Unique identifier of the unified profile. Omit when creating a new profile. |
| `unifiedProfile` | `contact` | Object (`ContactInfo`) | No | Contact information of the profile. |
| `unifiedProfile.contact` | `firstName` | String | No | First name of the profile. |
| `unifiedProfile.contact` | `lastName` | String | No | Last name of the profile. |
| `unifiedProfile.contact` | `maidenName` | String | No | Maiden name of the profile. |
| `unifiedProfile.contact` | `fullName` | String | No | Full name of the profile. |
| `unifiedProfile.contact` | `email` | String | No | Email ID of the profile. |
| `unifiedProfile.contact` | `username` | String | No | Username of the profile. |
| `unifiedProfile.contact` | `phoneNo` | String | No | Phone number of the profile. |
| `unifiedProfile.contact` | `address` | Object (`Address`) | No | Address of the profile. |
| `unifiedProfile.contact` | `website` | Array[String] | No | List of websites for the profile. |
| `unifiedProfile.contact` | `phoneDetails` | Array[`PhoneDetail`] | No | Phone details for the profile. |
| `unifiedProfile.contact` | `emailDetails` | Array[`EmailDetail`] | No | Email details for the profile. |
| `unifiedProfile` | `profiles` | Array[`Profile`] | No | List of social identities linked to the profile. **This is the array that determines which channels the survey can be distributed over.** |
| `unifiedProfile.profiles[]` | `name` | String | **Yes**¹ | Name of the person. |
| `unifiedProfile.profiles[]` | `channelType` | String | **Yes**¹ | Channel type of the profile — for example `EMAIL`, `SMS`, `WHATSAPP_BUSINESS`. |
| `unifiedProfile.profiles[]` | `channelId` | String | **Yes**¹ | Unique identifier of the customer on that channel. **If the `channelId` is unique, a new profile is created and a journey is associated with it; otherwise the journey is associated with the existing profile.** |
| `unifiedProfile.profiles[]` | `permalink` | String | **Yes**¹ | Link of the profile on the social channel. |
| `unifiedProfile.profiles[]` | `avatarUrl` | String | No | Profile image link. |
| `unifiedProfile.profiles[]` | `profileImageUrl` | String | No | Profile image link. |
| `unifiedProfile.profiles[]` | `bio` | String | No | Detailed description about the user. |
| `unifiedProfile.profiles[]` | `followers` | Integer (int32) | No | Followers count of the user. |
| `unifiedProfile.profiles[]` | `following` | Integer (int32) | No | Count of users/pages followed by this user. |
| `unifiedProfile.profiles[]` | `username` | String | No | Unique identifier of the user. |
| `unifiedProfile.profiles[]` | `verified` | Boolean | No | `true` if the user is verified by the channel. Default `false`. |
| `unifiedProfile.profiles[]` | `unSubscribed` | Boolean | No | `true` if the user is subscribed for email and other activities. Default `false`. |
| `unifiedProfile.profiles[]` | `deleted` | Boolean | No | `true` if the profile is deleted natively. Default `false`. |
| `unifiedProfile.profiles[]` | `snCreatedTime` | Integer (int64) | No | Social channel created time (epoch milliseconds). |
| `unifiedProfile.profiles[]` | `snModifiedTime` | Integer (int64) | No | Social channel modified time (epoch milliseconds). |
| `unifiedProfile.profiles[]` | `statusCount` | Integer (int32) | No | Status count for the profile. |
| `unifiedProfile.profiles[]` | `accountSpecificInfos` | Array[`AccountSpecificInfo`] | No | Account-specific information. |
| `unifiedProfile` | `demographics` | Object (`Demographics`) | No | Demographic details of the profile. |
| `unifiedProfile` | `profileWorkflow` | Object (`ProfileWorkflow`) | No | Partner-level workflow container. |
| `unifiedProfile` | `createdTime` | Integer (int64) | No | Created time of the profile in Sprinklr (epoch milliseconds). |
| `unifiedProfile` | `modifiedTime` | Integer (int64) | No | Last modified time of the profile in Sprinklr (epoch milliseconds). |
| `unifiedProfile` | `customPropertiesMetadata` | Array[`CustomPropertyWithMetadata`] | No | Custom property details. |
| `unifiedProfile` | `restricted` | Boolean | No | Profile masked flag. |


¹ `name`, `channelType`, `channelId`, and `permalink` are listed in the `required` array of the `Profile` schema. Note that **no supplied example sends `permalink`** — including the V2 portal page, which marks it Optional, and the Help Center in-product sample. Treat the OpenAPI `required` list on `Profile` as unverified for this use case.

`UnifiedProfile` additionally carries `works`, `organizations`, `certificates`, `recommendations`, `educations`, `languages`, `skills`, `courses`, `honors`, `patents`, `projects`, `publications`, `testScores`, `voluntaryExp`, and `operatingHours`. None of these are referenced by any supplied CFM example; they are inherited from the shared profile model and are not documented further here. See the Profile API V3 guide for their semantics.

### 5.3 `Address` object

`unifiedProfile.contact.address`, schema `Address` — *Describes the schema for Address.*

| Parameter | Type | Required | Description |
|  --- | --- | --- | --- |
| `street1` | String | No | First line of the user's address. |
| `street2` | String | No | Second line of the user's address. |
| `city` | String | No | The city of the user's address, to help identify the location. |
| `state` | String | No | The state of the user's address. |
| `country` | String | No | The country of the user's address. |
| `postalCode` | String | No | ZIP code of the address. |


### 5.4 `AccountSpecificInfo` object

`unifiedProfile.profiles[].accountSpecificInfos[]`, schema `AccountSpecificInfo`.

| Parameter | Type | Required | Description |
|  --- | --- | --- | --- |
| `accountId` | Integer (int64) | No | Account ID of the profile. |
| `externalId` | String | No | External ID of the profile. |
| `lastBrandEngagedTime` | Integer (int64) | No | Last brand engagement time (epoch milliseconds). |
| `lastFanEngagedTime` | Integer (int64) | No | Last fan engagement time (epoch milliseconds). |
| `optIn` | Boolean | No | `true` if opted in. Default `false`. |
| `fanSubscriptionState` | String | No | Subscription state of the fan. |
| `activeUser` | Boolean | No | `true` if the user is active. Default `false`. |
| `invited` | Boolean | No | `true` if invited. Default `false`. |


### 5.5 `ProfileWorkflow` and `ProfileSpaceWorkflow`

`unifiedProfile.profileWorkflow`, schema `ProfileWorkflow` — *Describes the schema of partner-level workflow in profile.*

| Parameter | Type | Required | Description |
|  --- | --- | --- | --- |
| `profileLists` | Array[Integer (int64)] | No | Partner profile lists on the profile, if any. |
| `customProperties` | Object (map of String → Array[String]) | No | Partner custom properties on the profile, if any. **Profile-level custom fields are not currently supported** (per V2 documentation). |
| `profileSpaceWorkflows` | Array[`ProfileSpaceWorkflow`] | No | List of client-level workflows on the profile, if any. |


`unifiedProfile.profileWorkflow.profileSpaceWorkflows[]`, schema `ProfileSpaceWorkflow`:

| Parameter | Type | Required | Description |
|  --- | --- | --- | --- |
| `spaceId` | String | **Yes** | Client ID. The only required field on this schema. |
| `modifiedTime` | Integer (int64) | No | Last modified time of the space workflow (epoch milliseconds). |
| `customProperties` | Object (map of String → Array[String]) | No | Client custom properties on the asset, if any. |
| `queues` | Array[`Queue`] | No | Client queue details of the message, if any. |
| `profileLists` | Array[Integer (int64)] | No | Client profile lists on the profile, if any. |
| `tags` | Array[String] | No | Client tags on the profile, if any. |


### 5.6 Example request

```bash
curl --request POST \
  --url 'https://api3.sprinklr.com/{env}/api/v3/cfmWorkflow/triggerWithNewProfile' \
  --header 'Authorization: {{accessToken}}' \
  --header 'Key: {{apiKey}}' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json' \
  --data-raw '{
    "workflowId": "595b4041-6eba-400f-aff0-797f1029c6f2",
    "contextParams": {
      "IGNORE_DEDUP": true,
      "lang": "ar",
      "country": "Jordan",
      "countryCode": "SA",
      "surveyFilled": "true"
    },
    "unifiedProfile": {
      "contact": {
        "firstName": "Alex",
        "lastName": "Doe",
        "email": "alex.doe@example.com",
        "phoneNo": "9876543210"
      },
      "profiles": [
        {
          "name": "Alex Doe",
          "channelType": "EMAIL",
          "channelId": "alex.doe@example.com"
        }
      ]
    }
  }'
```

**Multi-channel variant** — attach several channel identities so the workflow can select a distribution channel:

```json
{
  "workflowId": "{{workflowId}}",
  "contextParams": {
    "IGNORE_DEDUP": true,
    "lang": "en",
    "country": "India",
    "countryCode": "IN",
    "surveyFilled": "false"
  },
  "unifiedProfile": {
    "contact": {
      "firstName": "Alex"
    },
    "profiles": [
      { "channelType": "WHATSAPP_BUSINESS", "channelId": "918012345678", "name": "Alex Doe" },
      { "channelType": "SMS",               "channelId": "918012345678", "name": "Alex Doe" },
      { "channelType": "EMAIL",             "channelId": "alex.doe@example.com", "name": "Alex Doe" }
    ]
  }
}
```

### 5.7 Example response

```json
{
  "data": "Success",
  "errors": []
}
```

### 5.8 Response parameters

| Parameter | Type | Description |
|  --- | --- | --- |
| `data` | String | Indicates the outcome of the API request. `"Success"` when the workflow was triggered for the profile. |
| `errors` | Array[`Error`] | Contains any errors encountered during the request. Empty when no errors occurred. |
| `metadata` | Object (`ResponseMetadata`) | Response metadata. Declared on the `APIResponse` envelope; absent from every supplied example. |


## 6. Response format and status codes

### 6.1 The V3 envelope

Both operations declare the shared **`APIResponse`** schema:

```json
{
  "data": {},
  "errors": [],
  "metadata": {}
}
```

| Field | Type | Description |
|  --- | --- | --- |
| `data` | Object | Operation result. For both CFM Workflow operations this is the string `"Success"`. |
| `errors` | Array[`Error`] | Array of error objects. Empty when no errors occurred. |
| `metadata` | Object (`ResponseMetadata`) | Response metadata. |


### 6.2 Response codes

Declared in the OpenAPI specification for **both** operations:

| HTTP code | Scenario | Description |
|  --- | --- | --- |
| `200 OK` | Success | The CFM workflow was triggered successfully. |
| `400 Bad Request` | Invalid parameters | Missing `workflowId`, malformed JSON, or an invalid `contextParams`/`unifiedProfile` payload. |
| `401 Unauthorized` | Authentication failed | Invalid or missing `Authorization` token. |
| `403 Forbidden` | Insufficient permissions | The caller lacks the permission required to trigger the workflow. |
| `404 Not Found` | Not found | No matching workflow for the supplied `workflowId`. |


For the full status-code catalogue see [REST API Error and Status Codes](https://dev.sprinklr.com/) on the developer portal.

## 7. Reference values

### 7.1 `channelType` values used in CFM distribution

| Value | Channel | Typical `channelId` |
|  --- | --- | --- |
| `EMAIL` | Email survey distribution | Email address, e.g. `alex.doe@example.com` |
| `SMS` | SMS survey distribution | Phone number in international format, e.g. `918012345678` |
| `WHATSAPP_BUSINESS` | WhatsApp Business survey distribution | Phone number in international format, e.g. `918012345678` |


These three are the channels named in the CFM Workflow API description and used in the V2 and Help Center samples. `channelType` on the `Profile` schema is declared as an open `type: string`, not a closed enum, so the platform-wide channel list also applies. **Values are uppercase and case-sensitive.**

### 7.2 Conventional `contextParams` keys

| Key | Type in examples | Meaning |
|  --- | --- | --- |
| `IGNORE_DEDUP` | Boolean | Ignore duplicate detection during workflow execution. |
| `lang` | String | Language code used to localize workflow behavior or content, e.g. `ar`, `en`. |
| `country` | String | Country name used as contextual input, e.g. `Jordan`. |
| `countryCode` | String | Two-letter country code, e.g. `SA`, `IN`. |
| `surveyFilled` | String | Whether the survey has been completed, e.g. `"true"`. |


`contextParams` is an **open map**. Any additional key you pass becomes available as a workflow variable to the workflow's conditions and actions. Add extra keys through **Test API Connection** in the workflow record to see them reflected in a generated request.

### 7.3 Workflow actions and conditions reachable from a trigger

Once triggered, the workflow can run any of the elements supported by the CFM Workflow API (Audience Profile) event:

| Bucket | Element | Description |
|  --- | --- | --- |
| Journey Processes | **Trigger Survey Distribution** | Selects an already-created trigger-based survey distribution on Email, SMS, or WhatsApp and fires it based on the workflow conditions. |
| Journey Processes | Custom Field Actions | Sets case or profile custom fields directly, or copies them from workflow variables. |
| Journey Processes | Update Properties | Updates supported custom properties, attributes, or metadata from workflow variables. |
| Journey Processes | Decision Box | Adds a decision point to branch on specific conditions. |
| Communication | Send Resolved Message | Sends a follow-up email, SMS, or WhatsApp message, customizable with workflow variables. |
| Records | Get Records | Retrieves data from Sprinklr entity records for use in later actions or conditions. |
| Utility | Go to Node | Directs flow to a specific node, allowing custom paths. |
| Utility | Add or remove from queues | Adds or removes cases from queues based on workflow conditions. |
| Actions | End Event | Marks the end of the workflow. |
| Actions | Create Record | Creates a new record from workflow information. |
| Actions | Update Record | Modifies an existing record based on triggers or conditions. |


(Source: [Setting Up a CFM Workflow API Event Workflow](https://www.sprinklr.com/help/articles/setting-workflow-trigger-events/setting-up-a-cfm-workflow-api-event-workflow/6807458589cac71a44d0022c))

## 8. Use cases

#### 8.1 Cart-abandonment follow-up

A customer abandons a shopping cart. Your commerce platform calls `POST /cfmWorkflow/triggerWithNewProfile` with the shopper's contact details and `contextParams` describing the cart. The workflow updates the profile and triggers a personalized survey or incentive over email or SMS to encourage the customer to complete the purchase. If the customer responds, the team follows up with targeted offers or addresses the issue that caused the abandonment.

#### 8.2 Post-purchase feedback collection

After a purchase completes, your order-management system triggers the workflow with transaction context. The workflow sends a personalized survey over the customer's preferred channel. Use `contextParams` to carry order value, product category, and store identifier so the workflow's conditions can route high-value orders to a longer survey.

#### 8.3 Cross-channel customer-journey insight

Send a trigger after each key interaction — purchase, profile update, service visit. Because every trigger consolidates into the same unified profile (keyed on `channelId`), you accumulate a complete view of the customer's interactions across channels while still gathering point-in-time feedback.

#### 8.4 Known customer, no profile payload

Your CRM already synchronizes profiles into Sprinklr nightly. At event time you only need to fire the workflow. Use `POST /cfmWorkflow/trigger` with `workflowId` and `contextParams` only — no profile construction, smaller payload, fewer moving parts. **This case had no V2 equivalent.**

#### 8.5 Localized survey distribution

Set `lang`, `country`, and `countryCode` in `contextParams`. The workflow branches on these values to select a localized survey template and an appropriate distribution channel per market — for example the `"lang": "ar"`, `"country": "Jordan"`, `"countryCode": "SA"` combination used in the reference examples.

#### 8.6 Suppressing deduplication for a deliberate re-send

Set `"IGNORE_DEDUP": true` when you intentionally want a second survey to reach a customer who has already been contacted — for example a re-survey after a service recovery. Leave it unset (or `false`) for normal traffic so the platform's duplicate detection protects the customer from survey fatigue.

#### 8.7 Multi-channel fallback

Attach `WHATSAPP_BUSINESS`, `SMS`, and `EMAIL` identities in a single `profiles[]` array, as in the (#56-example-request) multi-channel variant. The workflow's distribution action can then choose the channel, and you have not had to decide it at trigger time.

#### 8.8 Verifying an integration before go-live

Open the workflow record, choose **Test API Connection**, fill in channel type, first name, full name, social network user ID, and any extra `contextParams`, then click **Get API Request**. The `workflowId` is filled in automatically. Add your authentication headers and run the generated request from Postman. A successful execution confirms the API connection before you wire the trigger into your production system flow.

#### 8.9 Support-case-closure feedback

When your ticketing system closes a case, trigger the workflow with the case reference in `contextParams`. The workflow sends a post-support satisfaction survey and, based on the response, can create a follow-up record or route the customer to a recovery journey.