activating-datacloud
forcedotcom/sf-skills
Manage Salesforce Data Cloud activations, targets, and downstream delivery of audiences and data.
What is activating-datacloud?
This skill handles the Act phase of Data Cloud workflows—activations, activation targets, data actions, and pushing Data Cloud outputs to downstream systems. Use it when managing audience delivery and data action configuration, not for segment creation or data retrieval.
- Create and manage activations to deliver Data Cloud audiences downstream
- Configure activation targets and data-action targets for external platforms
- Inspect available platforms and verify downstream delivery setup
- Validate upstream segment health before creating downstream assets
- Diagnose org readiness for Act phase work using the shared classifier
How to install activating-datacloud
npx skills add https://github.com/forcedotcom/sf-skills --skill activating-datacloud- External community sf data360 CLI plugin installed
- Data Cloud-enabled Salesforce org
- Published upstream segment or insight (before creating activations)
- Destination platform credentials and configuration (outside Data Cloud CLI)
How to use activating-datacloud
- 1.Run the readiness classifier to verify org is ready for Act phase work
- 2.Inspect available activation platforms and existing targets using list commands
- 3.Create the activation target or data-action target definition first
- 4.Create the activation or data action referencing the target
- 5.Verify downstream readiness by listing activations and inspecting data flow
Use cases
- Push a published Data Cloud segment to a marketing platform via activation target
- Set up a data action to trigger downstream workflows in an external system
- Verify that an activation is healthy and data is flowing to the destination
- Inspect available activation platforms and targets in the current org
- Create deterministic destination definitions for reusable audience delivery
- Data Cloud administrators managing audience activation
- Marketing operations engineers configuring downstream delivery
- Integration specialists setting up data action targets
- Salesforce developers building Data Cloud workflows
activating-datacloud FAQ
Use activating-datacloud for downstream delivery, activations, and data actions. Use segmenting-datacloud when building or modifying the audience or insight itself.
This means the activation surface is gated for your org or user. Focus on activation setup, permissions, and destination configuration instead of retrying the creation command.
Yes. Destination configuration (target definition) should come before activation creation. Inspect available platforms first to understand what targets are available.
No. Use segmenting-datacloud for segment creation and retrieving-datacloud for data retrieval and search work. This skill is only for Act phase downstream delivery.
Start with read-only inspection commands (list, inspect) rather than mutating operations. This is the safest approach when destination setup is uncertain.
Full instructions (SKILL.md)
Source of truth, from forcedotcom/sf-skills.
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)." 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
- exploring query/search or search indexes → retrieving-datacloud
- setting up base connections or ingestion → connecting-datacloud, preparing-datacloud
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 ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json. - Inspect available platforms and targets before mutating activation setup.
- Keep destination definitions deterministic and reusable where possible.
- Treat downstream credential and platform constraints as separate validation concerns.
- Prefer read-only inspection first when the destination state is unclear.
Recommended Workflow
1. Classify readiness for act work
node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json
2. Inspect destinations first
sf data360 activation platforms -o <org> 2>/dev/null
sf data360 activation-target list -o <org> 2>/dev/null
sf data360 data-action-target list -o <org> 2>/dev/null
3. Create the destination before the activation
sf data360 activation-target create -o <org> -f target.json 2>/dev/null
sf data360 data-action-target create -o <org> -f target.json 2>/dev/null
4. Create the activation or data action
sf data360 activation create -o <org> -f activation.json 2>/dev/null
sf data360 data-action create -o <org> -f action.json 2>/dev/null
5. Verify downstream readiness
sf data360 activation list -o <org> 2>/dev/null
sf data360 activation data -o <org> --name <activation> 2>/dev/null
High-Signal Gotchas
- Activation design depends on a healthy published upstream segment.
- Destination configuration usually comes before activation creation.
- Downstream credential and platform constraints may live outside the Data Cloud CLI alone.
- Read-only inspection is the safest first move when the destination setup is unclear.
CdpActivationTargetorCdpActivationExternalPlatformmeans the activation surface is gated for the current org/user; guide the user toward activation setup, permissions, and destination configuration instead of retrying blindly.
Output Format
Act task: <activation / activation-target / data-action / data-action-target>
Destination: <platform or target>
Target org: <alias>
Artifacts: <definition files / commands>
Verification: <listed / created / blocked>
Next step: <destination validation or downstream testing>
References
- README.md
- ../orchestrating-datacloud/assets/definitions/activation-target.template.json
- ../orchestrating-datacloud/assets/definitions/activation.template.json
- ../orchestrating-datacloud/assets/definitions/data-action-target.template.json
- ../orchestrating-datacloud/assets/definitions/data-action.template.json
- ../orchestrating-datacloud/UPSTREAM.md
- ../orchestrating-datacloud/references/plugin-setup.md
- ../orchestrating-datacloud/references/feature-readiness.md
Related skills
More from forcedotcom/sf-skills and the wider catalog.
analyzing-omnistudio-dependencies
Detect namespaces, map dependencies, and visualize impact across OmniScripts, FlexCards, Integration Procedures, and Data Mappers.
applying-cms-brand
Search, extract, and apply Salesforce CMS brand guidelines to generated content.
applying-slds
Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons. Use when building any UI that needs SLDS, choosing between Lightning Base Components and SLDS Blueprints, applying styling hooks for theming, using utility classes for layout and spacing, or selecting icons. Triggers include \"build a modal\", \"create a form\", \"data table\", \"SLDS styling\", \"style with hooks\", \"add an icon\".
building-mobile-apps
Route to the right Salesforce mobile SDK (Mobile SDK or Agentforce SDK) for iOS or Android apps.
building-omnistudio-callable-apex
Build and review System.Callable Apex for Salesforce Industries OmniStudio with 120-point scoring.
building-omnistudio-datamapper
Create and validate OmniStudio Data Mappers (Extract, Transform, Load, Turbo Extract) with 100-point scoring.