Activating Datacloud
Wire Salesforce Data Cloud segments and data actions to downstream activation targets using the sf data360 CLI.
Overview
activating-datacloud is an agent skill for the Build phase that guides Salesforce Data Cloud activation, activation-target, and data-action delivery using sf data360 CLI workflows.
Install
npx skills add https://github.com/forcedotcom/sf-skills --skill activating-datacloudWhat is this skill?
- Guides activations, activation targets, data actions, and data-action targets in Data Cloud
- Includes ready-to-run sf data360 list and inspect commands with org alias (-o)
- Points to shared activation, activation-target, and data-action-target JSON templates in orchestrating-datacloud
- Covers troubleshooting when an activation is not ready before push
- Shared JSON templates for activation, activation-target, and data-action-target definitions in orchestrating-datacloud a
Adoption & trust: 596 installs on skills.sh; 513 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have segments or data actions in Data Cloud but cannot see which targets exist, push an activation, or explain why downstream delivery is blocked.
Who is it for?
Builders or admins who already have a Salesforce org alias and need repeatable activation and data-action target setup without re-reading scattered Data Cloud docs.
Skip if: Teams with no Salesforce CLI, no Data Cloud license, or needs limited to upstream ingestion only—use the broader orchestrating-datacloud family skills first.
When should I use this skill?
User asks to activate segments, manage activation or data-action targets, inspect downstream platforms, or debug activation readiness in Salesforce Data Cloud.
What do I get? / Deliverables
You get inspectable activation inventory, template-backed target definitions, and CLI steps to activate segments or wire data-action targets to downstream platforms.
- Documented activation and target configuration steps
- CLI command sequences for list and inspect operations
- References to filled activation or data-action-target definition JSON from templates
Recommended Skills
Journey fit
Activation setup is integration work you do while building or extending a CDP-connected product, not a pre-build validation exercise. Listing platforms, activation targets, activations, and data-action targets maps directly to third-party and platform integration subphase work.
How it compares
Use for activation push and target wiring—not as a generic CRM API skill or a local SQLite integration.
Common Questions / FAQ
Who is activating-datacloud for?
Salesforce-focused builders, integrators, and indie consultants who automate Data Cloud activation and downstream delivery from an agent with shell access to sf CLI.
When should I use activating-datacloud?
Use it during Build integrations when you must activate a segment, list activation targets, create a data-action target, or inspect why an activation is not ready—typically after models and segments exist in the org.
Is activating-datacloud safe to install?
Treat it like any skill that runs org-scoped CLI commands against production data paths; review the Security Audits panel on this page and restrict org aliases and secrets in your agent environment.
SKILL.md
READMESKILL.md - Activating Datacloud
# Credits & Acknowledgments This skill is part of the `*-datacloud` family. Shared attribution, upstream source mapping, and maintenance notes live in: - [../orchestrating-datacloud/CREDITS.md](../orchestrating-datacloud/CREDITS.md) - [../orchestrating-datacloud/UPSTREAM.md](../orchestrating-datacloud/UPSTREAM.md) # activating-datacloud Activation and downstream delivery workflows for Salesforce Data Cloud. ## Use this skill for - activations - activation targets - data actions - data action targets - downstream platform inspection before push ## Example requests ```text "Activate this segment to the downstream platform" "Show me what activation targets already exist" "Create a data action target for this integration" "Help me inspect why this activation is not ready" ``` ## Common commands ```bash sf data360 activation platforms -o myorg 2>/dev/null sf data360 activation-target list -o myorg 2>/dev/null sf data360 activation list -o myorg 2>/dev/null sf data360 data-action-target list -o myorg 2>/dev/null ``` ## References - [SKILL.md](SKILL.md) - [../orchestrating-datacloud/assets/definitions/activation-target.template.json](../orchestrating-datacloud/assets/definitions/activation-target.template.json) - [../orchestrating-datacloud/assets/definitions/activation.template.json](../orchestrating-datacloud/assets/definitions/activation.template.json) - [../orchestrating-datacloud/assets/definitions/data-action-target.template.json](../orchestrating-datacloud/assets/definitions/data-action-target.template.json) - [../orchestrating-datacloud/assets/definitions/data-action.template.json](../orchestrating-datacloud/assets/definitions/data-action.template.json) - [../orchestrating-datacloud/references/plugin-setup.md](../orchestrating-datacloud/references/plugin-setup.md) - [CREDITS.md](CREDITS.md) --- name: activating-datacloud description: "Salesforce Data Cloud Act phase. Use this skill when the user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. TRIGGER when: user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. DO NOT TRIGGER when: the task is segment creation (use segmenting-datacloud), data retrieval/search work (use retrieving-datacloud), or STDM/session tracing (use observing-agentforce)." license: MIT compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org" metadata: version: "1.0" --- # activating-datacloud: Data Cloud Act Phase Use this skill when the user needs **downstream delivery work**: activations, activation targets, data actions, or pushing Data Cloud outputs into other systems. ## When This Skill Owns the Task Use `activating-datacloud` when the work involves: - `sf data360 activation *` - `sf data360 activation-target *` - `sf data360 data-action *` - `sf data360 data-action-target *` - verifying downstream delivery setup Delegate elsewhere when the user is: - still building the audience or insight → [segmenting-datacloud](../segmenting-datacloud/SKILL.md) - exploring query/search or search indexes → [retrieving-datacloud](../retrieving-datacloud/SKILL.md) - setting up base connections or ingestion → [connecting-datacloud](../connecting-datacloud/SKILL.md), [preparing-datacloud](../preparing-datacloud/SKILL.md) --- ## Required Context to Gather First Ask for or infer: - target org alias - destination platform or downstream system - whether the segment already exists and is published - whether the user needs create, inspect, update, or delete - whether the task is activation-focused or data-action-focused --- ## Core Operating Rules - Verify the upstream segment or insight is healthy before creating downstream delivery assets. - Run the shared readiness classifier before mutating activation assets: `node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json`. - Inspect available p