forcedotcom/sf-skills / plugins/builder/service-engagement/skills/service-digital-engagement-deployment-configure
service-digital-engagement-deployment-configure
VerifiedConfigures Embedded Messaging Deployments for Messaging for In-App and Web (MIAW). Use when the user needs to create a new embedded messaging deployment from scratch using Connect API with defaults, or update an existing deployment's settings using Metadata API. Produces Connect API request payloads for new deployments and EmbeddedServiceConfig metadata XML for updates. TRIGGER when the user mentions embedded messaging deployment, embedded service deployment, MIAW deployment, messaging widget setup, chat widget configuration, embedded chat deployment, or references a .EmbeddedServiceConfig-meta.xml file. DO NOT TRIGGER when the user is creating a messaging channel (use service-digital-engagement-channel-configure), configuring legacy Live Agent embedded service, or generating the JavaScript code snippet for website embedding.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.0 KB |
| assets/esd_api_mobile_template.xml | config | 1.4 KB |
| assets/esd_web_update_template.xml | config | 5.7 KB |
| examples/esd_api.xml | config | 1.4 KB |
| examples/esd_mobile.xml | config | 1.4 KB |
| examples/esd_web_full.xml | config | 1.5 KB |
| examples/esd_web_prechat_fields.xml | config | 3.3 KB |
| references/branding_and_tooling.md | markdown | 3.9 KB |
| references/code_snippet.md | markdown | 2.8 KB |
| references/connect_api_creation.md | markdown | 5.1 KB |
| references/deployment_settings.md | markdown | 7.3 KB |
| references/onboarding_contract.md | markdown | 9.1 KB |
| references/prechat_forms.md | markdown | 21.7 KB |
| scripts/check-api-version.shexecutable | script | 1.6 KB |
assets/esd_web_update_template.xml
View on GitHub<?xml version="1.0" encoding="UTF-8"?>
<EmbeddedServiceConfig xmlns="http://soap.sforce.com/2006/04/metadata">
<areGuestUsersAllowed>false</areGuestUsersAllowed>
<!-- Branding (optional — reference an existing BrandingSet) -->
<!-- To set branding, add a branding element whose value is {BRANDING_SET_NAME} -->
<deploymentFeature>EmbeddedMessaging</deploymentFeature>
<deploymentType>{Web|API|Mobile}</deploymentType>
<!-- Pre-Chat Form (OPTIONAL) -->
<!-- Pre-chat is OFF by default. DELETE this entire block if the deployment
collects no pre-chat data (that is the correct default).
Each formField must resolve to a standard parameter (_-prefixed) OR an
existing customParameter on the channel below. ChoiceList fields also need
a choiceList record that ALREADY EXISTS in the org (created in Setup —
it is not a deployable artifact). -->
<embeddedServiceForms>
<displayContext>Conversation</displayContext>
<!-- 1. Standard field -->
<embeddedServiceFormFields>
<displayOrder>0</displayOrder>
<formField>_FirstName</formField>
<formFieldType>Text</formFieldType>
<isHidden>false</isHidden>
<isRequired>true</isRequired>
<messagingChannelParameterType>Standard</messagingChannelParameterType>
</embeddedServiceFormFields>
<!-- 2. Visible custom text field (formField = an existing channel customParameter name) -->
<embeddedServiceFormFields>
<displayOrder>1</displayOrder>
<formField>{CUSTOM_PARAM_NAME}</formField>
<formFieldType>Text</formFieldType>
<isHidden>false</isHidden>
<isRequired>false</isRequired>
<messagingChannelParameterType>Custom</messagingChannelParameterType>
</embeddedServiceFormFields>
<!-- 3. Checkbox custom field -->
<embeddedServiceFormFields>
<displayOrder>2</displayOrder>
<formField>{CHECKBOX_PARAM_NAME}</formField>
<formFieldType>Checkbox</formFieldType>
<isHidden>false</isHidden>
<isRequired>false</isRequired>
<messagingChannelParameterType>Custom</messagingChannelParameterType>
</embeddedServiceFormFields>
<!-- 4. ChoiceList (dropdown) field — choiceList DeveloperName must already exist in the org -->
<embeddedServiceFormFields>
<choiceList>{CHOICELIST_DEVELOPER_NAME}</choiceList>
<displayOrder>3</displayOrder>
<formField>{CHOICELIST_PARAM_NAME}</formField>
<formFieldType>ChoiceList</formFieldType>
<isHidden>false</isHidden>
<isRequired>true</isRequired>
<messagingChannelParameterType>Custom</messagingChannelParameterType>
</embeddedServiceFormFields>
<!-- 5. Hidden / pre-populated field — displayOrder=-1, value captured but never shown -->
<embeddedServiceFormFields>
<displayOrder>-1</displayOrder>
<formField>{HIDDEN_PARAM_NAME}</formField>
<formFieldType>Text</formFieldType>
<isHidden>true</isHidden>
<isRequired>false</isRequired>
<messagingChannelParameterType>Custom</messagingChannelParameterType>
</embeddedServiceFormFields>
<isActive>true</isActive>
</embeddedServiceForms>
<!-- Messaging Channel Configuration -->
<embeddedServiceMessagingChannel>
<!-- Display name shown when pre-chat is enabled (OPTIONAL — delete this line if unused).
EXACTLY 3 brace tokens; leave unused slots EMPTY, e.g. {_firstName}{_lastName}{}.
Each non-empty token = a pre-chat field's externalParameterName (Channel Variable Name),
NOT the formField value. Standard: _firstName / _lastName / _email / _subject
(lowercase-first — the _FirstName formField spelling is REJECTED).
Custom: the channel param's externalParameterName (usually its name, e.g. CompanyName). -->
<displayNameFormat>{DISPLAY_NAME_FORMAT}</displayNameFormat>
<isChatInvitationCustomizable>{true|false}</isChatInvitationCustomizable>
<isEnabled>true</isEnabled>
<isInvitationEnabled>{true|false}</isInvitationEnabled>
<isSendInvtAllowedAfterAccept>{true|false}</isSendInvtAllowedAfterAccept>
<isSendInvtAllowedAfterReject>{true|false}</isSendInvtAllowedAfterReject>
<messagingChannel>{CHANNEL_PLATFORM_KEY}</messagingChannel>
<!-- shouldShow* / shouldStartNewLineOnEnter below: keep the retrieved value on update; with nothing retrieved, leave at the default false.
Set true only if the user explicitly asks for that feature. -->
<shouldShowAgentforceTagline>false</shouldShowAgentforceTagline>
<shouldShowDeliveryReceipts>false</shouldShowDeliveryReceipts>
<shouldShowEmojiSelection>false</shouldShowEmojiSelection>
<shouldShowReadReceipts>false</shouldShowReadReceipts>
<shouldShowTypingIndicators>false</shouldShowTypingIndicators>
<shouldStartNewLineOnEnter>false</shouldStartNewLineOnEnter>
</embeddedServiceMessagingChannel>
<isEnabled>true</isEnabled>
<isTermsAndConditionsEnabled>{true|false}</isTermsAndConditionsEnabled>
<isTermsAndConditionsRequired>{true|false}</isTermsAndConditionsRequired>
<masterLabel>{DEPLOYMENT_NAME}</masterLabel>
<shouldHideAuthDialog>false</shouldHideAuthDialog>
<!-- Web only: copy the site value UNCHANGED from the retrieved config (required for Web, can never be
changed). Omit this element entirely for Mobile/API deployments. -->
<site>{EXISTING_SITE_NAME}</site>
</EmbeddedServiceConfig>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |