Agent skill · forcedotcom
service-digital-engagement-deployment-configure
Configures 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.
What it needs
About 8k tokens when loaded.
What this skill does
Configuring Embedded Messaging Deployment Configures EmbeddedServiceConfig metadata for Salesforce Messaging for In-App and Web (MIAW). Supports two distinct workflows: creating new deployments via Connect API and updating existing deployments via Metadata API. Scope In scope: Creating new Embedded Service Deployments (API, Mobile, Web types) via Connect API; updating existing deployments with forms, branding, channel settings, and features via Metadata API; generating EmbeddedServiceConfig XML for updates Out of scope: Creating the messaging channel itself (use service-digital-engagement-channel-configure), publishing deployments (Connect API post-step), creating Experience Sites (Connect API prerequisite for Web type) --- Clarifying Questions Before generating, ask the user if not already clear: Create or update? Are you creating a new deployment or updating an existing one? Deployment type? API (headless), Mobile (native apps), or Web (browser widget)? Channel name? What is the channelPlatformKey of the messaging channel to associate? For create: What should the deployment be named? For update: What features to configure? (pre-chat forms, business hours, T&C, UI toggles) For update (Web): What is the Experience Site name? Branding overrides needed? --- Required Inputs Gather or infer before proceeding: Operation: create or update Deployment type: API, Mobile, or Web Deployment name: Used for masterLabel and the API name Channel name: The channelPlatformKey of the associated messaging channel For update operations additionally: Site name (Web only): The Experience Site name (format ESW<name><timestamp>) Branding name (optional): Reference to existing BrandingSet Pre-chat form fields (optional): Field names and required status Business hours (optional): Name of existing BusinessHours record Defaults unless specified: isEnabled: true deploymentFeature: EmbeddedMessaging --- Workflow All steps are sequential. Do not skip or reorder. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-digital-engagement-deployment-configure--768cec