custom-notification-types SKILL.md skillA
custom-notification-types 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/custom-notification-types@v1.2.0Pins v1.2.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/custom-notification-types/SKILL.md- Versions recorded
- 5
- Latest version
- v1.2.0, committed Sep 5, 2026
- First version recorded
- May 9, 2026
- Size
- 13,111 bytes
- Repository stars
- 19
- License
- a license file GitHub does not identify
Custom Notification Types for desktop/mobile push alerts from Flow or Apex: type creation, target channels, Messaging.CustomNotification invocation, recipient limits, bulk notification patterns. NOT for choosing channels, consent, or notification-fatigue policy — use admin/custom-notification-type-design. NOT for email alerts — use admin/email-templates-and-alerts. Trigger keywords: notiftype, notificationtypes directory, customNotifTypeName, customNotificationAction, setNotificationTypeId…
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
# Custom Notification Types Activate when designing push or desktop notifications triggered from Flow, Apex, or process automation. Custom Notification Types replaced the older Chatter-only notification path; they support both desktop and mobile push channels, can be invoked from Flow or Apex, and have specific recipient limits that bite at scale. ## Before Starting - **Define the notification type in Setup first.** Without a CustomNotificationType record, neither Flow nor Apex can send. - **Know what the 500 cap counts.** `send(Set<String> users)` takes at most 500 *values*, and a Group or Queue Id is one value that fans out to every active member (Apex Reference Guide, `apexrefguide.txt:166766-166781`). - **Choose channels.** Desktop and Mobile are independent checkboxes; Mobile requires the Salesforce mobile app and enabled push notifications. ## Questions to Ask Before Configuring Ask these before creating the type; the answers decide the metadata, the send path, and the test. An LLM that skips them produces a type that deploys clean and delivers to nobody. | Ask | Why it matters | What a good answer adds | |---|---|---| …
Read the whole file at its exact version.
How to install
mdr add pranavnagrecha/awesomesalesforceskills/custom-notification-types@sha256:fbd98cf431efb8f3The line at the top of this page pins the label v1.2.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_g66fj3g6zkqgsbbm)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 9, 2026 and Sep 5, 2026, about one every 30 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.0 latest | 2026-09-05 | 427f4ea | 13,111 B | A | view · diff |
| v1.1.0 | 2026-08-14 | 25df1fd | 5,747 B | A | view · diff |
| v1.1.0 | 2026-05-19 | 8e3d8a5 | 5,699 B | A | view · diff |
| v1.0.0 | 2026-05-12 | 7a159d7 | 5,712 B | A | view · diff |
| v1.0.0 | 2026-05-09 | c3c14d8 | 5,699 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 (13111 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_g66fj3g6zkqgsbbm GET https://markdownregistry.com/api/v1/resolve?ref=pranavnagrecha/awesomesalesforceskills/custom-notification-types GET https://markdownregistry.com/api/v1/blob/fbd98cf431efb8f3b04578e600cbf87857ea8e5eca62c635997f87808548b0a8
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.