forcedotcom/sf-skills / plugins/builder/service-engagement/skills/service-digital-engagement-messaging-site-integrate
service-digital-engagement-messaging-site-integrate
VerifiedIntegrates a Messaging for In-App and Web (MIAW) Embedded Messaging chat widget into an Experience Cloud site by patching the site's LWR or Aura page bundle, deploying, publishing, and verifying guest access. Use when the user wants to embed messaging on an Experience site, add a chat widget to a community, place the Embedded Messaging component on an LWR or Aura page, wire an embedded service deployment to a site, references the retrieved bundle artifacts (`content.json`, `homeGuestLayout.json`, or a `*.site-meta.xml` file), or automates the retrieve/patch-JSON/deploy/publish flow instead of clicking through Experience Builder. DO NOT TRIGGER when creating the messaging channel (use service-digital-engagement-channel-configure), when creating or updating the EmbeddedServiceConfig deployment (use service-digital-engagement-deployment-configure), or when generating a standalone JavaScript snippet for a non-Experience website.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.9 KB |
| references/aura_patch.md | markdown | 2.4 KB |
| references/bundle_detection.md | markdown | 2.5 KB |
| references/deploy_and_publish.md | markdown | 3.6 KB |
| references/lwr_patch.md | markdown | 3.7 KB |
| references/lwr_route_scaffolding.md | markdown | 1.8 KB |
| references/manual_fallback.md | markdown | 3.0 KB |
| scripts/detect_bundle_type.shexecutable | script | 1.1 KB |
| scripts/patch_aura_bundle.shexecutable | script | 4.1 KB |
| scripts/patch_lwr_bundle.shexecutable | script | 7.3 KB |
references/manual_fallback.md
View on GitHub# Manual Fallback — Experience Builder Deep Link
Use this fallback when any automated step fails: bundle undetectable, patch write blocked, deploy fails and cannot be repaired, publish fails, or the guest URL smoke test never returns `200`.
Print the deep link and verbatim instructions below to the user. Do **not** claim the messaging widget is live on the site until the user has confirmed they completed the Publish step in Experience Builder.
## Resolve org-specific values
Never hardcode either value. Query them per run:
- **`MyDomain`** — take the `Instance URL` (or `Login URL`) from:
```bash
sf org display --target-org <org-alias>
```
Strip protocol and trailing slash. Typical form: `<mydomain>.lightning.force.com`.
- **`Network.Id`** — query by URL path prefix:
```bash
sf data query --query \
"SELECT Id FROM Network WHERE UrlPathPrefix='<urlPath>' LIMIT 1" \
--target-org <org-alias>
```
## Deep link template
Substitute the resolved values into:
```text
https://<MyDomain>.lightning.force.com/sfsites/picasso/core/config/commeditor.apexp?...networkId=<Network.Id>
```
The `...` in the path represents any additional query-string parameters the org may require (some orgs redirect through an intermediate SSO step); take them from the org's own Experience Builder URL rather than fabricating them.
## Verbatim user instructions
Provide the user the following steps (adapt the deployment name to the one they supplied):
1. Open the deep link above. Salesforce may prompt for login; use an admin credential for the target org.
2. Once Experience Builder opens on the target site's home page, use the left-hand **Components** panel and drag the **Embedded Messaging** component onto the page. Drop it into the main content region — most templates render it at the bottom right regardless of exact drop position.
3. In the right-hand **Property panel** that appears after the drop:
- **Deployment** — pick the deployment named `<deploymentName>` from the picklist. If it is not listed, confirm the Embedded Service Deployment has been published via Connect API.
- Leave `Hide Chat Button on Load` set to **Default** unless the user needs the button hidden.
- Leave `Auth Mode` unchecked for public sites (equivalent to `isExpSiteAuthMode: false`).
4. Click **Publish** in the top-right of Experience Builder. Confirm the publish dialog.
5. Wait 30–60 seconds for propagation, then reload the site's public URL. The chat button should appear.
## Reporting back
Once the user confirms publish in Experience Builder, re-run the guest URL smoke test:
```bash
curl -sL -o /dev/null -w "%{http_code}" \
https://<domainHostname>/<urlPath>
```
Report success only when the response is `200`. If the user reports the button still does not appear, gather:
- The specific step where the automated flow failed.
- The `sf project deploy report` output (if a deploy was attempted).
- The `Network.Name` and `Network.Id` values used.
These are the minimum context needed to escalate to platform support.
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 |