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 |
examples/esd_web_prechat_fields.xml
View on GitHub<!--
Pre-chat forms delta. This is NOT a standalone deployable file; graft it onto a base
Web deployment (see esd_web_full.xml for everything else: branding, site, etc.). Two pieces:
1. embeddedServiceForms goes directly under EmbeddedServiceConfig.
2. displayNameFormat goes INSIDE the existing embeddedServiceMessagingChannel (not
directly under EmbeddedServiceConfig). Merge it into that element if the base file
already has one; do not add a second embeddedServiceMessagingChannel.
-->
<embeddedServiceForms>
<displayContext>Conversation</displayContext>
<embeddedServiceFormFields>
<displayOrder>0</displayOrder>
<formField>_FirstName</formField>
<formFieldType>Text</formFieldType>
<isHidden>false</isHidden>
<isRequired>true</isRequired>
<messagingChannelParameterType>Standard</messagingChannelParameterType>
</embeddedServiceFormFields>
<embeddedServiceFormFields>
<displayOrder>1</displayOrder>
<formField>_LastName</formField>
<formFieldType>Text</formFieldType>
<isHidden>false</isHidden>
<isRequired>true</isRequired>
<messagingChannelParameterType>Standard</messagingChannelParameterType>
</embeddedServiceFormFields>
<embeddedServiceFormFields>
<displayOrder>2</displayOrder>
<formField>_Email</formField>
<formFieldType>Email</formFieldType>
<isHidden>false</isHidden>
<isRequired>true</isRequired>
<messagingChannelParameterType>Standard</messagingChannelParameterType>
</embeddedServiceFormFields>
<embeddedServiceFormFields>
<displayOrder>3</displayOrder>
<formField>CompanyName</formField>
<formFieldType>Text</formFieldType>
<isHidden>false</isHidden>
<isRequired>false</isRequired>
<messagingChannelParameterType>Custom</messagingChannelParameterType>
</embeddedServiceFormFields>
<embeddedServiceFormFields>
<displayOrder>4</displayOrder>
<formField>NewsletterOptIn</formField>
<formFieldType>Checkbox</formFieldType>
<isHidden>false</isHidden>
<isRequired>false</isRequired>
<messagingChannelParameterType>Custom</messagingChannelParameterType>
</embeddedServiceFormFields>
<embeddedServiceFormFields>
<choiceList>Customer_Inquiry_Type</choiceList>
<displayOrder>5</displayOrder>
<formField>InquiryType</formField>
<formFieldType>ChoiceList</formFieldType>
<isHidden>false</isHidden>
<isRequired>true</isRequired>
<messagingChannelParameterType>Custom</messagingChannelParameterType>
</embeddedServiceFormFields>
<embeddedServiceFormFields>
<displayOrder>-1</displayOrder>
<formField>utm_campaign</formField>
<formFieldType>Text</formFieldType>
<isHidden>true</isHidden>
<isRequired>false</isRequired>
<messagingChannelParameterType>Custom</messagingChannelParameterType>
</embeddedServiceFormFields>
<isActive>true</isActive>
</embeddedServiceForms>
<!-- displayNameFormat tokens use each field's externalParameterName (e.g. _firstName),
NOT the formField spelling above (e.g. _FirstName). -->
<embeddedServiceMessagingChannel>
<displayNameFormat>{_firstName}{_lastName}{}</displayNameFormat>
</embeddedServiceMessagingChannel>
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 |