forcedotcom/sf-skills / skills/service-de-channel-routing-configure
service-de-channel-routing-configure
VerifiedConfigure routing on a newly-inserted Enhanced `MessagingChannel` so activation will accept it. Given a `{CHANNEL_ID}`, walks through picking a routing type (Omni-Channel Queue, Omni-Flow, Agentforce Service Agent, Digital Worker, or direct User), locates or provisions the target, then PATCHes `SessionHandlerId` (plus `FallbackQueueId` where required). Use between insertion and activation — activation fails server-side with `nullQueueId`/`LiveMessageSetupException` if no valid `SessionHandlerId` is set. Do not use for full end-to-end setup — use `service-de-headless-channel-configure`.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 22.7 KB |
| references/asa-routing.md | markdown | 4.3 KB |
| references/gotchas.md | markdown | 6.1 KB |
| references/named-queue.md | markdown | 2.2 KB |
| references/queue-creation.md | markdown | 5.1 KB |
| references/target-locate.md | markdown | 8.5 KB |
| references/worked-examples.md | markdown | 7.3 KB |
| scripts/tests/test_skill_contract.py | script | 834 B |
references/named-queue.md
View on GitHub---
name: service-de-channel-routing-configure-named-queue
description: "Load when the caller of service-de-channel-routing-configure supplied {QUEUE} (a queue the user already named) and it has to be validated on the Queue routing path. Covers matching it against the eligible list, the unfiltered lookup when it isn't eligible, the three-way prompt (use anyway / pick eligible / create new), and the warning added to the success envelope. DO NOT load when no {QUEUE} was supplied — the normal Stage 3-Queue list applies."
metadata:
version: "1.0"
related-skills: service-de-channel-routing-configure
---
# Validating a queue the user named (`{QUEUE}`)
Match `{QUEUE}` against the Stage 3-Queue eligible list by `Id`, `DeveloperName`, or `Name`.
- **Match** → record `{QUEUE_ID}`, skip to Stage 5, no prompt.
- **No match** → look it up without the eligibility filters:
```bash
sf data query --target-org '{ORG_ALIAS}' \
--query "SELECT Id, Name, DeveloperName, QueueRoutingConfigId FROM Group WHERE Type='Queue' AND (DeveloperName='{QUEUE}' OR Name='{QUEUE}')" \
--json
```
If `{QUEUE}` is an Id (15 or 18 chars starting with `00G`), filter on `Id='{QUEUE}'` instead. Don't combine the two: comparing `Id` to a name fails the whole query with `INVALID_QUERY_FILTER_OPERATOR` ("invalid ID field").
If it exists, tell the user exactly what's missing. Never silently accept it, and never silently fall through to "create new":
```text
Queue '{QUEUE}' exists but isn't set up for messaging: {"it doesn't list Messaging Session as a supported object" | "it has no Omni-Channel routing configuration"}.
The server will accept it, but the skill can't confirm sessions will route there.
1) Use it anyway
2) Pick an eligible queue from the list
3) Create a new messaging queue
```
On (1), record `{QUEUE_ID}`, add `"warning": "queue is not MessagingSession-capable / Omni-enabled"` to the success envelope, and continue to Stage 5. (2) → the normal numbered list. (3) → `references/queue-creation.md`.
- **No queue matches `{QUEUE}` at all** → say so, then show the normal numbered list.
Why the rule and the server disagree: see `references/gotchas.md` #10.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |