Agent skill · forcedotcom
service-omni-routing-flow-deploy
Use to deploy an Omni-Channel routing Flow for Case or VoiceCall and verify it routes work items to a queue or by skill. Supports the Case and VoiceCall steel thread with an autolaunched dryRun-gated variant and record-triggered QueueBased and SkillsBased variants. --trigger deploys a record-triggered variant; --routing-type SkillsBased evaluates WorkSkillRouting rules with a non-null skillOption; --runtime-proof checks routing evidence and, for SkillsBased, SkillRequirement rows. Triggers: deploy Omni routing flow for Case, deploy Omni routing flow for VoiceCall, wire VoiceCall routing, create a record-triggered Omni routing flow, verify a Case routing flow, deploy skills-based routing flow. Do not use for screen flows, platform-event-triggered flows, or Flow Tests.
What it needs
About 6k tokens when loaded.
What this skill does
service-omni-routing-flow-deploy Voice runtime proof depends on a provisioned Contact Center. Flow redeploys report Changed even when the deployed configuration is unchanged. Deploy an Omni-Channel routing Flow via the Metadata API, confirm it lands Active, and prove it routes work — either by CLI invocation (the autolaunched dry-run) or by observing real routing side effects (the record-triggered variant). service-omni-channel-setup-coordinate wires it in after service-omni-queue-deploy has produced the target queue and its members are bound. Variants Four assets ship under assets/force-app/main/default/flows/ — an autolaunched and a record-triggered variant for each of Case and VoiceCall. Selection is by --target Case VoiceCall (default Case) and --trigger. Variant Shape Proves Routes real work? --- --- --- --- OmniRouteCases / OmniRouteVoiceCalls (default) Autolaunched, dryRun gate CLI invocability via Actions REST, no side effects No OmniRouteCaseTrigger / OmniRouteVoiceCallTrigger (--trigger) Record-triggered on insert, calls routeWork Real routing — the insert creates PendingServiceRouting/AgentWork Yes The autolaunched variant de-risks the headless CLI path cheaply; the record-triggered variant proves real records reach a queue. A full steel thread deploys the record-triggered variant. With --trigger --routing-type SkillsBased, the record-triggered variant is drawn from a sibling <FlowDN>.SkillsBased.flow-meta.xml asset that emits routingType=SkillsBased plus a non-null skillOption. The base trigger flows hardcode routingType=QueueBased, so a skills-based-routing org config never takes effect at runtime — this variant is what makes it route by skill (W-24069467). Inputs --target Case VoiceCall (default Case) — selects the flow pair. --trigger — deploy the record-triggered variant with dynamic token resolution. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-omni-routing-flow-deploy