Skip to content

forcedotcom/sf-skills / skills/service-de-headless-channel-configure

service-de-headless-channel-configure

Verified

Top-level orchestrator: given a messaging channel type and its inputs, produces an activated Enhanced `MessagingChannel` in the target org — without the Meta/LINE/Apple setup popups. Prompts for `{MESSAGE_TYPE}` if not supplied, then sequences insert → route → consent → activate → requested settings (auto-responses, keywords, session inactivity) via the type-agnostic dispatcher (`service-de-channel-create`) plus the shared routing/settings/activation leaves, and reports every requested setting as configured, not applicable, or failed. Resumes from partial state on re-run. Use to set up an Enhanced channel (WhatsApp, Facebook, LINE, Apple, SMS) end-to-end, bypassing in-org setup popups. Do not use for a single stage of an already-inserted channel — use the matching leaf skill (`service-de-channel-activate`, `service-de-channel-settings-configure`, `service-de-channel-routing-configure`) instead.

references/requested-settings.md

View on GitHub
---
name: service-de-headless-channel-configure-requested-settings
description: "Load when running Stage 4.5 of the headless channel setup orchestrator (the request asked for auto-responses, messaging keywords, or session inactivity) or rendering those settings in the Stage 5 report. Covers what to forward to service-de-channel-settings-configure, per-type applicability, the configured / notApplicable / failed classification, the known Facebook metadata defect, and the report block. DO NOT load for the consent facet, which runs before activation in Stage 3.5."
metadata:
  version: "1.0"
  related-skills: service-de-headless-channel-configure
---

# Requested settings (Stage 4.5 + Stage 5)

## Invoke the settings leaf once

Invoke `service-de-channel-settings-configure` **once**, with:

- `{CHANNEL_ID}`, `{ORG_ALIAS}`
- `{FACETS}` = the requested subset of `auto-responses`, `keywords`, `inactivity`
- the values from the request (response text per `<type>`, `responseTimeoutInMins`, keyword lists,
  timeout minutes). Forward them, and don't invent defaults for values the user didn't give.

The leaf enforces per-type applicability. For the types this orchestrator creates, **the idle and
inactive-session timeouts are MIAW-only**, so they never apply here. Only
`isAgentMessageResetInactivityEnabled` applies, and only on Apple and Facebook. Expect
`facet-not-applicable` for the rest and report it. That's correct behavior, not a failure.

## Classify each requested item

| Leaf outcome for the item | Bucket |
| --- | --- |
| In `facetsConfigured` and verified, or `noop: true` | `configured` |
| `facet-not-applicable` | `notApplicable` (with the leaf's `hint`) |
| `metadata-deploy-failed` / `verify-failed` / any other `ok:false` | `failed` (with the leaf's `kind` + `message` verbatim) |

**Never fail the run here.** The channel is already live. Append `"settings"` to `STEPS_RUN` if
anything was configured, and carry failures to Stage 5 as warnings.

**Facebook:** Facebook channels currently reject real metadata changes with an opaque numeric error
like `(-462367322)` (see `service-de-channel-settings-configure` `references/gotchas.md` #16). Report
it as `failed` with the leaf's hint, and don't retry.

## Stage 5 report block

Add `"settings": {"configured": [...], "notApplicable": [...], "failed": [...]}` to the success
envelope (shape in `references/output-envelopes.md`). Below the standard success lines, render:

```text
   Requested settings:
   - Configured: {each configured item}
   - Not applicable to {MESSAGE_TYPE}: {each item} — {reason}
   - Failed: {each item} — {kind}: {message}
```

If any item is `failed`, lead the report with
`Warning: channel is live, but {N} requested setting(s) were not applied` instead of an unqualified
`Success`, and add the same text to the envelope's `warnings`. **Every item captured in Stage 0 must
appear in exactly one bucket.** Check the count before rendering.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall