Skip to content

forcedotcom/sf-skills / plugins/builder/service-engagement/skills/service-email-to-case-configure

service-email-to-case-configure

Verified

Use 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.

assets/CaseSettings.settings-meta.xml

View on GitHub
<?xml version="1.0" encoding="UTF-8"?>
<!-- Template for headless Email-to-Case config. Fill in, then emit a COMMENT-FREE
     source file (see SKILL.md step 3). fullName is implicitly "Case". Do not set
     emailAddress (supply via --routing-email), emailServicesAddress, or isVerified. -->
<CaseSettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <!-- Support Settings (siblings of emailToCase). Set inline whatever the user
         names; omit the rest. Default Case Owner: defaultCaseOwner (a Username or
         Queue DeveloperName) with its defaultCaseOwnerType (User or Queue).
         Automated Case User — pick ONE, they are mutually exclusive:
           - a named person -> defaultCaseUser (a Username), OR
           - the org's System user -> useSystemUserAsDefaultCaseUser true, plus
             systemUserEmail when the user gives an email (do NOT also set
             defaultCaseUser in this case).
         apply-casesettings.py can also supply/validate these via flags and
         preserves existing org values. Emit these fields ONLY when the user
         names a value; a defaultCaseOwnerType without a defaultCaseOwner (or the
         reverse) is a half-filled owner the platform rejects. -->

    <!-- "Enable Email Drafts" — plural, top-level. Remove if the user opts out. -->
    <enableDraftEmails>true</enableDraftEmails>

    <emailToCase>
        <!-- Required. On-Demand must be on before addresses bind. -->
        <enableEmailToCase>true</enableEmailToCase>
        <enableOnDemandEmailToCase>true</enableOnDemandEmailToCase>

        <!-- Optional convenience toggles (on by default). Remove any the user opts out of. -->
        <enableHtmlEmail>true</enableHtmlEmail>
        <notifyOwnerOnNewCaseEmail>true</notifyOwnerOnNewCaseEmail>
        <enableE2CDeduplicateAttachments>true</enableE2CDeduplicateAttachments>
        <showWordCountInComposer>true</showWordCountInComposer>

        <!-- One routingAddresses block per address. addressType: EmailToCase | Outlook
             | GmailOAuth. Optional per-address caseOwner + caseOwnerType (opt-in, paired)
             — see SKILL.md step 6. Placeholders below are filled per address. -->
        <routingAddresses>
            <addressType>EmailToCase</addressType>
            <routingName>ROUTING_NAME</routingName>
            <caseOrigin>CASE_ORIGIN</caseOrigin>
            <casePriority>CASE_PRIORITY</casePriority>
            <createTask>false</createTask>
            <saveEmailHeaders>true</saveEmailHeaders>
        </routingAddresses>
    </emailToCase>
</CaseSettings>
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 CodeCodexUnverifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall