forcedotcom/sf-skills / plugins/builder/service-engagement/skills/service-email-to-case-configure
service-email-to-case-configure
VerifiedUse to configure Salesforce Email-to-Case headlessly via the Metadata API. Reads CaseSettings, applies the emailToCase config with updateMetadata, and verifies by re-reading. Also the entry point for attaching an Agentforce agent to Email-to-Case: configures the E2C base, then delegates agent creation and channel wiring. TRIGGER on set up/configure Email-to-Case, enable E2C routing addresses, add a routing address, or E2C with an Agentforce agent. DO NOT TRIGGER for the interactive Easy Setup wizard, On-Demand E2C only, general Case/web-to-case setup, or an agent with no E2C involved.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.5 KB |
| assets/CaseSettings.settings-meta.xml | config | 2.5 KB |
| examples/CaseSettings-two-addresses.settings-meta.xml | config | 1.8 KB |
| references/apply-mechanics.md | markdown | 4.8 KB |
| references/routing_address_reference.md | markdown | 7.4 KB |
| references/troubleshooting.md | markdown | 5.1 KB |
| scripts/apply-casesettings.py | script | 65.1 KB |
| scripts/check-agent-email-capability.shexecutable | script | 1.8 KB |
| scripts/tests/__init__.py | script | 0 B |
| scripts/tests/_bootstrap.py | script | 1.5 KB |
| scripts/tests/_fakeorg.py | script | 15.2 KB |
| scripts/tests/_run.py | script | 2.7 KB |
| scripts/tests/test_apply_org_scenarios.py | script | 33.6 KB |
| scripts/tests/test_get_session.py | script | 5.1 KB |
| scripts/tests/test_new_capabilities.py | script | 8.0 KB |
| scripts/tests/test_validate_casesettings.py | script | 7.3 KB |
| scripts/validate-casesettings.py | script | 10.6 KB |
examples/CaseSettings-two-addresses.settings-meta.xml
View on GitHub<?xml version="1.0" encoding="UTF-8"?>
<!--
Example: Email-to-Case enabled with two routing addresses (EmailToCase + Outlook).
This is the source-file shape that apply-casesettings.py consumes.
Note what is and is NOT here:
1. The two required emailToCase switches (enableEmailToCase + enableOnDemandEmailToCase)
and, on each address, the required addressType / routingName / caseOrigin / casePriority.
2. NO emailAddress on either address. The customer-facing emails are supplied at apply
time via one routing-email option per address, in this document order (first the
Support Inbox email, then the Sales Outlook Inbox email). See SKILL.md step 9.
3. Support Settings (Default Case Owner / Automated Case User) appear here only when the
user names them — this example names none, so none are set. When named, write the
paired fields (defaultCaseOwner + defaultCaseOwnerType, etc.); fields the org already
has are preserved when omitted. Never defaulted to the authenticated user.
-->
<CaseSettings xmlns="http://soap.sforce.com/2006/04/metadata">
<emailToCase>
<enableEmailToCase>true</enableEmailToCase>
<enableOnDemandEmailToCase>true</enableOnDemandEmailToCase>
<routingAddresses>
<addressType>EmailToCase</addressType>
<routingName>Support Inbox</routingName>
<caseOrigin>Email</caseOrigin>
<casePriority>Medium</casePriority>
<createTask>false</createTask>
<saveEmailHeaders>true</saveEmailHeaders>
</routingAddresses>
<routingAddresses>
<addressType>Outlook</addressType>
<routingName>Sales Outlook Inbox</routingName>
<caseOrigin>Email</caseOrigin>
<casePriority>High</casePriority>
</routingAddresses>
</emailToCase>
</CaseSettings>
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 | Unverified | 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 |