Newer Version Available
MessagingChannel
Parent Type
File Suffix and Directory Location
MessagingChannel components have the suffix messagingChannel and are stored in the messagingChannels folder.
Version
MessagingChannel components are available in API version 55.0 and later.
Special Access Rules
This type is available if your org has the “Configure Messaging” and “View Setup and Configuration” permissions for Messaging enabled.
Fields
| Field Name | Description |
|---|---|
| automatedResponses |
|
| customParameters |
|
| description |
|
| masterLabel |
|
| messagingChannelType |
|
| sessionHandlerFlow |
|
| sessionHandlerQueue |
|
| sessionHandlerType |
|
| standardParameters |
|
MessagingAutoResponse
Represents an automatic response used in a channel.
| Field Name | Description |
|---|---|
| response |
|
| type |
|
MessagingChannelCustomParameter
Represent a custom parameter added to a channel.
| Field Name | Description |
|---|---|
| actionParameterMappings |
|
| externalParameterName |
|
| masterLabel |
|
| maxLength |
|
| name |
|
| parameterDataType |
|
MessagingChannelActionParameterMapping
Represents a mapping between a parameter and an Omni-Channel flow or agent task.
| Field Name | Description |
|---|---|
| actionParameterName |
|
MessagingChannelStandardParameter
Represents a standard parameter used to pass information into a channel.
| Field Name | Description |
|---|---|
| actionParameterMappings |
|
| externalInteractionId |
|
| externalInteractionName |
|
| externalInteractionType |
|
| parameterType |
|
Declarative Metadata Sample Definition
The following is an example of a MessagingChannel component. This messaging channel passes custom and standard parameters from the messaging channel to a flow, and it routes to a flow with a fallback queue.
1<?xml version="1.0" encoding="UTF-8"?>
2<MessagingChannel xmlns="http://soap.sforce.com/2006/04/metadata">
3 <automatedResponses>
4 <response>Hello there!</response>
5 <type>InitialResponse</type>
6 </automatedResponses>
7 <automatedResponses>
8 <response>Your agent is looking into the issue now.</response>
9 <type>AgentEngagedResponse</type>
10 </automatedResponses>
11 <automatedResponses>
12 <response>Bye!</response>
13 <type>AgentEndEngagementResponse</type>
14 </automatedResponses>
15 <customParameters>
16 <actionParameterMappings>
17 <actionParameterName>Flow_PhoneNumber</actionParameterName>
18 </actionParameterMappings>
19 <externalParameterName>PhoneNumber</externalParameterName>
20 <masterLabel>Phone Number</masterLabel>
21 <name>PhoneNumber</name>
22 <parameterDataType>Number</parameterDataType>
23 </customParameters>
24 <masterLabel>Initial Message</masterLabel>
25 <messagingChannelType>EmbeddedMessaging</messagingChannelType>
26 <sessionHandlerFlow>FlowName</sessionHandlerFlow>
27 <sessionHandlerQueue>FallbackQueueName</sessionHandlerQueue>
28 <sessionHandlerType>Flow</sessionHandlerType>
29 <standardParameters>
30 <actionParameterMappings>
31 <actionParameterName>Flow_LastName</actionParameterName>
32 </actionParameterMappings>
33 <parameterType>LastName</parameterType>
34 </standardParameters>
35 <standardParameters>
36 <actionParameterMappings>
37 <actionParameterName>Flow_FirstName</actionParameterName>
38 </actionParameterMappings>
39 <parameterType>FirstName</parameterType>
40 </standardParameters>
41 <standardParameters>
42 <actionParameterMappings>
43 <actionParameterName>Flow_Email</actionParameterName>
44 </actionParameterMappings>
45 <parameterType>Email</parameterType>
46 </standardParameters>
47 <standardParameters>
48 <actionParameterMappings>
49 <actionParameterName>Flow_Subject</actionParameterName>
50 </actionParameterMappings>
51 <parameterType>Subject</parameterType>
52 </standardParameters>
53</MessagingChannel>If you route the messaging channel to a queue, there’s no fallback flow.
1<?xml version="1.0" encoding="UTF-8"?>
2<MessagingChannel xmlns="http://soap.sforce.com/2006/04/metadata">
3 <masterLabel>EmbeddedChannel2</masterLabel>
4 <messagingChannelType>EmbeddedMessaging</messagingChannelType>
5 <sessionHandlerQueue>DemoQueueName</sessionHandlerQueue>
6 <sessionHandlerType>Queue</sessionHandlerType>
7</MessagingChannel>The following is an example package.xml that references the previous definition.
1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3 <types>
4 <members>*</members>
5 <name>MessagingChannel</name>
6 </types>
7 <version>55.0</version>
8</Package>Wildcard Support in the Manifest File
This metadata type supports the wildcard character * (asterisk) in the package.xml manifest file. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.