email-service-inbound SKILL.md skillA
email-service-inbound from pranavnagrecha/awesomesalesforceskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pranavnagrecha/awesomesalesforceskills/email-service-inbound@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pranavnagrecha/awesomesalesforceskills
- Path
skills/admin/email-service-inbound/SKILL.md- Versions recorded
- 3
- Latest version
- v1.1.0, committed Sep 5, 2026
- First version recorded
- May 5, 2026
- Size
- 27,094 bytes
- Repository stars
- 19
- License
- a license file GitHub does not identify
Inbound email processing in Salesforce via Email Services + the `Messaging.InboundEmailHandler` Apex interface. Covers EmailService configuration (running user, accept-from address, attachment handling, error / failure routing), the EmailServicesAddress per-routing-address pattern, the handler's `Messaging.InboundEmail` payload (text body, HTML body, headers, attachments, in-reply-to threading), and the canonical Email-to-Case alternative for case creation. NOT for outbound email…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Inbound Email Service Salesforce can accept inbound email and run Apex against each message. The mechanism: an **Email Service** (org-level configuration) maps one or more **Email Service Addresses** (the local-part + Salesforce-supplied domain) to a class implementing `Messaging.InboundEmailHandler`. Apex receives the parsed email, returns a `Messaging.InboundEmailResult`, and the platform responds (delivery success, error reply, drop) accordingly. The classic alternative is **Email-to-Case** — a built-in service that creates a Case from each email, with extensive admin configuration (auto-response, routing, threading, contact lookup). Email-to-Case is the right answer for case creation; custom email service is the right answer for everything else (file uploads, custom-object creation, audit logging, complex routing). What this skill is NOT. Outbound email — `admin/email-templates-and-alerts`. Email-to-Case-specific configuration — `admin/email-to-case-configuration`. This skill is the custom-handler path. --- ## Before Starting - **Decide custom service vs Email-to-Case.** Case creation? E2C is built; don't reinvent. Anything else? Custom service. …
Read the whole file at its exact version.
How to install
mdr add pranavnagrecha/awesomesalesforceskills/email-service-inbound@sha256:26cd4c21e3b3e48fThe line at the top of this page pins the label v1.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_djas26jxgennukij)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 5, 2026 and Sep 5, 2026, about one every 61 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-09-05 | 928a6bc | 27,094 B | A | view · diff |
| v1.0.0 | 2026-08-14 | 25df1fd | 14,560 B | A | view · diff |
| v1.0.0 | 2026-05-05 | a4c56f1 | 14,494 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (27094 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pranavnagrecha/awesomesalesforceskills · 19 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_djas26jxgennukij GET https://markdownregistry.com/api/v1/resolve?ref=pranavnagrecha/awesomesalesforceskills/email-service-inbound GET https://markdownregistry.com/api/v1/blob/26cd4c21e3b3e48f40f9c549abe11543add9f984ae89de2642860ca50a7d62ca
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.