Update to CrowdStrike Falcon Foundry
Snapshot Nov 4, 2026 · 12:08 UTC · version 1.7.0
Collection source: downloaded plugin package.
Instructions updated for workflows-development
Full description — Now says: Falcon Fusion SOAR", "add an on-demand workflow", runs `foundry workflows create`, or needs help with Falcon
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Oct 8, 2026 · 18:03 UTC
Fusion SOAR", "add an on-demand workflow", runs `foundry workflows create`, or needs help with
Nov 4, 2026 · 12:08 UTC
Falcon Fusion SOAR", "add an on-demand workflow", runs `foundry workflows create`, or needs help with Falcon
Skill instructions
Oct 8, 2026 · 18:03 UTC
Fusion SOAR", "add an on-demand workflow", runs `foundry workflows create`, or needs help with Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropr...
Nov 4, 2026 · 12:08 UTC
Falcon Fusion SOAR", "add an on-demand workflow", runs `foundry workflows create`, or needs help with Falcon Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — u...
Supporting files
Oct 8, 2026 · 18:03 UTC
[{"relative_path":"references/action-discovery.md","size_in_bytes":3322},{"relative_path":"references/advanced-patterns.md","size_in_bytes":8801},{"relative_path":"references/cel-expressions.md","size_in_bytes":2678},{"relative_path":"re...
Nov 4, 2026 · 12:08 UTC
[{"relative_path":"references/action-discovery.md","size_in_bytes":4055},{"relative_path":"references/advanced-patterns.md","size_in_bytes":14479},{"relative_path":"references/cel-expressions.md","size_in_bytes":4838},{"relative_path":"r...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,8 +1,8 @@ --- name: workflows-development -description: Create and configure Falcon Fusion SOAR workflow YAML for Falcon Foundry apps. TRIGGER when user asks to "create a workflow", "build an automation", "configure Fusion SOAR", "add an on-demand workflow", runs `foundry workflows create`, or needs help with Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropriate sub-skill. -version: 1.6.0 -updated: 2026-10-01 +description: Create and configure Falcon Fusion SOAR workflow YAML for Falcon Foundry apps. TRIGGER when user asks to "create a workflow", "build an automation", "configure Falcon Fusion SOAR", "add an on-demand workflow", runs `foundry workflows create`, or needs help with Falcon Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropriate sub-skill. +version: 1.7.0 +updated: 2026-10-30 tags: [foundry, workflows, fusion-soar, yaml] author: CrowdStrike license: MIT @@ -13,18 +13,15 @@ # Foundry Workflows Development -> Write every workflow definition in Fusion YAML, validate step dependencies before running it, and handle failures with conditional routing and action-level flags ([Error Handling](#error-handling)) — Fusion has no `onError` blocks and no built-in retry. +> Write every workflow definition in Falcon Fusion YAML, validate step dependencies before running it, and handle failures with conditional routing and action-level flags ([Error Handling](#error-handling)) — Fusion has no `onError` blocks and no built-in retry. > **Part of a suite.** If `development-workflow` has not already run, and this is a new app or its first capability, load the `development-workflow` skill first — it owns the CLI prerequisite check, scaffolding order, and manifest coordination. -Falcon Foundry Workflows are YAML-defined automation units executed by the Falcon Fusion engine. They orchestrate multi-step operations across Functions, Collections, CrowdStrike APIs, and RTR sessions with parallelism and state management. - ## Prerequisites - **Workflow Author role** is required in addition to the Falcon Developer role -- Workflows are YAML templates that can be provisioned as active workflow instances -- Up to **25 workflows** can be provisioned from a single template -- Set `provision_on_install: true` to auto-provision when the app is installed +- Workflows are YAML templates provisioned as active instances (up to **25** per template) +- **`provision_on_install: true` is REQUIRED** in the workflow YAML — treat it as a per-workflow checklist item, not a footnote. With `true`, installing the app creates the workflow in Falcon Fusion SOAR, turned on. With `false`, the deploy is "Successful" and the template is listed in the app's **Logic** section, but installing creates no workflow, so nothing runs until something provisions it (the `/workflows/system-definitions/provision` API). Use `false` deliberately: for a workflow with an action ID you can't verify, which the user finishes in the console (see [Platform Action Fallback Strategy](references/advanced-patterns.md#platform-action-fallback-strategy)), or to let an app install without the credentials a workflow needs, as the sample apps' e2e tests do. ## CLI Scaffolding @@ -43,37 +40,13 @@ foundry workflows triggers view --no-prompt # List triggers ``` -> **Always use `--no-prompt` on `actions view` and `triggers view`.** As of CLI 2.1.1, multiple matches are listed non-interactively. On older CLIs, partial matches trigger an interactive prompt that fails in headless environments (`Error: no TTY available`). The bundled `action_search.py` is an alternative that works without a manifest directory — see [references/action-discovery.md](references/action-discovery.md). +> **Always use `--no-prompt` on `actions view`/`triggers view`** — without it, multiple or partial matches trigger an interactive prompt that fails in headless environments (`Error: no TTY available`); as of CLI 2.1.1 matches are listed non-interactively. The bundled `action_search.py` works without a manifest directory — see [references/action-discovery.md](references/action-discovery.md). ## Workflow Structure ### Trigger + Actions Format (standard) -This is the format produced by `foundry workflows create` and used by all production Foundry sample apps: - -```yaml -name: list-okta-users -description: On-demand workflow to list Okta users and print results -provision_on_install: true -trigger: - next: - - list_users - name: On demand - type: On demand -actions: - list_users: - id: api_integrations.Okta.listUsers - next: - - print_results - properties: {} - version_constraint: ~0 - print_results: - id: aadbf530e35fc452a032f5f8acaaac2a - properties: - text_data: "${data['list_users.API_Integration.Custom_Okta.listUsers.body']}" - version_constraint: ~1 -output_fields: [] -``` +This is the format produced by `foundry workflows create` and used by many Foundry sample apps — a `trigger:` (with `next:` naming the first action) plus an `actions:` map where each action carries an `id`, `properties`, `version_constraint`, and optional `next:`, closing with `output_fields: []`. See [references/workflow-examples.md](references/workflow-examples.md#standard-trigger-actions-format) for the full canonical YAML (on-demand Okta list → print). **Trigger types:** @@ -82,285 +55,125 @@ | On demand | `name: On demand`, `type: On demand` | | Scheduled | `event: Schedule`, `schedule: {time_cycle: "0 */6 * * *", tz: Etc/UTC}` | -> **⚠️ Null-guard trigger parameters:** When run from the Falcon console, the UI prompts users to fill in parameters. However, when triggered via API or from another workflow, parameters may be empty. Guard defensively: -> -> ```yaml -> conditions: -> check_param: -> cel_expression: "data['param_name'] != null && data['param_name'] != ''" -> next: -> - use_param -> display: -> - param_name was provided -> else: -> - handle_missing -> ``` -> -> Or inline in CEL: `${data[?'param'].orValue("default")}` (preferred) or `${data['param'] != null ? data['param'] : "default"}` (traditional) - -**Variable syntax in actions:** Use `${data['action_key.path.to.field']}` CEL expressions. See [Variable References](#variable-references) for the full syntax. Do NOT use `$action_name.output.body` — it passes as a literal string and is not resolved. - -**Version constraints:** Every action requires `version_constraint`. The `~N` value pins against the activity's declared `semantic_version` field, not its internal iteration count. The rule: - -- `~0` = activity has **no** `semantic_version` defined (functions, API integrations, and some platform actions like "contain device") -- `~1` = activity **has** a `semantic_version` (most platform actions: Print data, Send email, Create/Update variable, Get device details, etc.) - -Use `foundry workflows actions view --name "<action>" --no-prompt` to check. If the activity output shows a semantic_version field, use `~1`. If it does not, use `~0`. +**Trigger parameters** (inputs the console prompts for when an on-demand workflow runs) are a JSON Schema object under `trigger:`, read in actions as `${data['name']}`: ```yaml -actions: - my_function: - id: functions.my-func.process - properties: {} - version_constraint: ~0 # no semantic_version defined - contain_host: - id: <contain-device-action-id> - properties: - device_id: "${data['trigger.device_id']}" - version_constraint: ~0 # no semantic_version defined - print_results: - id: aadbf530e35fc452a032f5f8acaaac2a +trigger: + name: On demand + type: On demand + parameters: + type: object properties: - text_data: "${data['my_function.output']}" - version_constraint: ~1 # has semantic_version + recipient: + type: string + description: Who gets the report + required: + - recipient ``` +> **⚠️ Null-guard trigger parameters:** When run from the Falcon console the UI prompts for parameters, but via API or from another workflow they may be empty. Guard with a `conditions:` branch (`cel_expression: data['param'] != null && data['param'] != ''`, routing to a handler via `else:`) or inline in CEL with a ternary: `${data['param'] != null ? data['param'] : "default"}`. Full `conditions:` block: [references/cel-expressions.md](references/cel-expressions.md#null-guard-trigger-parameters). + +**Variable syntax in actions:** Use `${data['action_key.path.to.field']}` CEL expressions. See [Variable References](#variable-references) for the full syntax. Do NOT use `$action_name.output.body` — it passes as a literal string and is not resolved. + +**Version constraints:** Set `version_constraint: ~N` on each action, where `N` is the major version of the activity's declared `semantic_version` (not its iteration count): **`~0`** when the activity has no `semantic_version` (functions, API integrations) or a `0.x` one (Contain device is `0.0.x`); **`~1`** for a `1.x` one (Print data, Send email, Create/Update variable, Get device details). Some samples omit it on function actions. Check with `scripts/action_search.py "<action>" --details`, which prints the `semantic_version` and the matching constraint; a worked `~0`/`~1` example is in [references/workflow-examples.md](references/workflow-examples.md#version-constraint-example). + ### Manifest Configuration ```yaml # manifest.yml workflows: - name: my-workflow - path: workflows/my-workflow/workflow.yaml + path: workflows/my-workflow.yml permissions: [] ``` Trigger type and schedule are defined inside the workflow YAML file (via `trigger:` block), not in the manifest. The manifest only declares the workflow name, path, and optional permissions. -For full RTR multi-host orchestration and investigation pipeline examples, see [references/workflow-examples.md](references/workflow-examples.md). - -> RTR scripts are not supported in certified Foundry apps (apps published to the CrowdStrike Store). RTR workflows work in custom/internal apps only. +> RTR scripts are not supported in certified Foundry apps (apps published to the CrowdStrike Store). RTR workflows work in custom/internal apps only. For full RTR multi-host orchestration and investigation-pipeline examples, see [references/workflow-examples.md](references/workflow-examples.md). ## Calling Functions from Workflows -Functions referenced in workflow actions (via `id: functions.{name}.{handler}`) must have `workflow_integration` in the manifest. This binds only at creation time, via `foundry functions create --wf-expose` (plus `--input-schema`/`--output-schema`) — hand-editing `manifest.yml` does not work. +Functions called via `id: functions.{name}.{handler}` must have `workflow_integration` in the manifest. Set it at create time with `foundry functions create --wf-expose` (plus `--input-schema`/`--output-schema`). For a function created without it whose schemas are already set, add the block to the handler in `manifest.yml` (`id: ""`, `disruptive`, `system_action`, `tags`, as `--wf-expose` writes it) and redeploy: the deploy fills in the `id` and binds it, including on a function that was already deployed without one. Missing it fails deploy with `referenced function '{name}' and handler '{handler}' does not have workflow_integration properties defined`. -If a function was created without it, recreate the function. That changes its `workflow_integration.id`, so update the `id: functions.{name}.{handler}` reference in your workflow YAML in place. Do NOT delete and recreate the workflow itself — see the warning below. +> **⚠️ Every non-empty `properties:` on a function action needs a declared `request_schema`.** A function action passes the handler only the properties its `request_schema` declares; an undeclared property is **silently dropped**, even with `additionalProperties: true`, and no error is raised. Symptom: a function that "runs fine" but behaves as if an input was blank. Declare every property the workflow passes. Declare the schema at create time via `foundry functions create … --input-schema` (hand-editing the manifest does not bind it). -**Deploy error if missing:** -``` -❌ Error: referenced function '{name}' and handler '{handler}' does not have workflow_integration properties defined -``` - -**Calling the app's own AI agent**: use `id: ai_agents.<agent name>` (the manifest `name`) with `input` for the prompt and `version_constraint: ~1`; the agent needs `exposure.workflows.system_action: true`. `apps validate` doesn't resolve it, so check the deploy output. See [workflow-invocation](../ai-agents-development/references/workflow-invocation.md). +**Calling the app's own AI agent**: `id: ai_agents.<agent name>` with `input` (the prompt) and `version_constraint: ~1`; the agent needs `exposure.workflows.system_action: true`, and its reply is read downstream as `${data['action_key.response']}`. `apps validate` doesn't resolve it — check the deploy output. Full walkthrough (aliasing, the `(2018) Action was not found` trap, `json_with_schema` field access) in the `ai-agents-development` skill's `references/workflow-invocation.md`. -> **⚠️ Reading Falcon alerts, detections, or incidents? It depends on whether the workflow already holds the object.** *Enriching* a detection the workflow was triggered on (query by its ID, e.g. `Ngsiem.detection.id = ?detectID`) → Event Query action, go schemaless. *Fetching a population you don't have* ("summarize all high-severity alerts") → source-of-truth API: a native platform action (e.g. Cases → Search Cases) first, or a FalconPy `Alerts`/`Detects` function when none fits — an Event Query can silently return nothing since NG-SIEM contents are connector-dependent. See [references/event-query-vs-api.md](references/event-query-vs-api.md). +> **⚠️ Reading Falcon alerts/detections/incidents? Depends on whether the workflow already holds the object.** *Enriching* one the workflow was triggered on (query by its ID) → Event Query action, schemaless. *Fetching a population you don't have* ("summarize all high-severity alerts") → source-of-truth API: a native platform action (e.g. Cases → Search Cases) or a FalconPy `Alerts`/`Detects` function — an Event Query can silently return nothing (NG-SIEM contents are connector-dependent). See [references/event-query-vs-api.md](references/event-query-vs-api.md). ## Calling API Integration Operations -> **💡 Consider HTTP Actions first.** For a simple REST call that doesn't need a custom UI or reusable function, an [HTTP Action](https://www.crowdstrike.com/tech-hub/ng-siem/build-api-integrations-with-falcon-fusion-soar-http-actions/) is faster than an API integration — no app, no OpenAPI spec, no deploy, and 130+ pre-built templates. Use a full API integration when the operation is reused across workflows or paired with functions/UI. See [references/http-actions.md](references/http-actions.md). - -Workflows invoke API integration operations using the `api_integrations.{name}.{operationId}` pattern: - -> **⚠️ Always use registered integrations.** If an API integration is declared in `manifest.yml`, the workflow MUST call it via `api_integrations.{name}.{operationId}`. Do NOT use a function that makes raw HTTP calls to the same API with hardcoded credentials or template variables like `{{API_TOKEN}}`. The platform manages authentication, rate limiting, and audit logging through the integration. +> **💡 Consider HTTP Actions first.** For a one-off REST call (no custom UI or reusable function), an [HTTP Action](https://www.crowdstrike.com/tech-hub/ng-siem/build-api-integrations-with-falcon-fusion-soar-http-actions/) is faster than an API integration — no app, no OpenAPI spec, no deploy, 130+ templates. Use a full API integration when the operation is reused across workflows or paired with functions/UI. See [references/http-actions.md](references/http-actions.md). -```yaml -actions: - list_users_action: - id: api_integrations.Okta.listUsers # {name}.{operationId} - properties: {} - version_constraint: ~0 - next: - - print_data - - print_data: - id: aadbf530e35fc452a032f5f8acaaac2a - properties: - text_data: "${data['list_users_action.API_Integration.Custom_Okta.listUsers.body']}" - version_constraint: ~1 -``` - -The `{name}` must exactly match the `name` field from the `api_integrations` entry in `manifest.yml`, prefixed with `Custom_`. The platform adds `Custom_` to all API integration names in the variable path. The OpenAPI spec must have a matching `operationId` with a properly structured `x-cs-operation-config`: - -```yaml -x-cs-operation-config: - workflow: - name: listUsers - description: List all users - expose_to_workflow: true - system: false -``` +> **⚠️ Always call a registered integration** via `api_integrations.{name}.{operationId}` — never a function making raw HTTP calls to the same API with hardcoded creds or `{{API_TOKEN}}`-style templates. The platform owns auth, rate limiting, and audit logging. -The `workflow` nesting is required — a flat `expose_to_workflow: true` under `x-cs-operation-config` will not work. Auth scopes for CLI-created artifacts are managed automatically. +`{name}` must match the manifest `api_integrations` entry, prefixed `Custom_` in the variable path (the platform adds it to every integration name). The action `id:` uses the `operationId`, but the next segment of the output path comes from the operation's `x-cs-operation-config.workflow.name` with spaces turned into underscores: an operation with `operationId: Get leavers data` and workflow name `Workday get leavers data` is called as `api_integrations.Workday get leavers data.Get leavers data` and read as `…API_Integration.Custom_Workday_get_leavers_data.Workday_get_leavers_data.body`. Copy the path from the editor's **Workflow data** panel. The OpenAPI `operationId`'s `x-cs-operation-config` must nest the config under a `workflow:` key (`name`, `description`, `expose_to_workflow: true`, `system: false`) — a flat `expose_to_workflow: true` will not work. Auth scopes for CLI-created artifacts are managed automatically. Full action + `x-cs-operation-config` example: [references/workflow-examples.md](references/workflow-examples.md#api-integration-operation-call). ## Platform Actions -Platform actions (send email, log output, create detection) require platform-specific action IDs. These IDs are verified identical across us-1, us-2, and eu-1 clouds: - -| Action Name | ID | -|------------|-----| -| Create variable | `702d15788dbbffdf0b68d8e2f3599aa4` | -| Update variable | `6c6eab39063fa3b72d98c82af60deb8a` | -| Print data | `aadbf530e35fc452a032f5f8acaaac2a` | -| Sleep | `4f1af1ae4c13dc1e3bcd725f8dc0f63b` | -| Send email | `07413ef9ba7c47bf5a242799f59902cc` | -| Request human input - Send email | `d6731c10b24834e2e0f4bd9d390a29c8` | -| Get device details | `6265dc947cc2252f74a5f25261ac36a9` | -| Contain device | `bec9fbeb4999d207937854fd56088107` | - -For actions not in this table, use `foundry workflows actions view --name "..." --no-prompt` or the API query in [references/action-discovery.md](references/action-discovery.md). There are 9,000+ platform actions available. MUST NOT guess action IDs — use discovery commands. +Platform actions (send email, log output, create detection) require platform-specific action IDs, verified identical across us-1, us-2, and eu-1. The two most used are **Print data** `aadbf530e35fc452a032f5f8acaaac2a` and **Send email** `07413ef9ba7c47bf5a242799f59902cc`; the full lookup table (Create/Update variable, Sleep, Get device details, Contain device, Request human input) is in [references/action-discovery.md](references/action-discovery.md#common-platform-action-ids). For any action not listed, use `foundry workflows actions view --name "..." --no-prompt`. There are 9,000+ platform actions — MUST NOT guess action IDs; use discovery commands. ### Common Action Properties -**Print data** (`aadbf530e35fc452a032f5f8acaaac2a`): - -Print data has three input properties: `fields` (array — dropdown of trigger/workflow metadata), `text_data` (string — general-purpose), and `custom_json` (object only). Use `text_data` for API integration responses since `body` may be an array. - -```yaml - print_data: - id: aadbf530e35fc452a032f5f8acaaac2a - properties: - text_data: "${data['list_users_action.API_Integration.Custom_Okta.listUsers.body']}" - version_constraint: ~1 -``` - -The data path follows the pattern: `action_key.API_Integration.Custom_{IntegrationName}.{operationId}.{field}`. The platform adds `Custom_` to all API integration names in the variable path. Use the **Workflow data** panel in the workflow editor to copy the exact path for any field — click the data pill and it copies the correct `${data['...']}` expression to your clipboard. - -**Send email** (`07413ef9ba7c47bf5a242799f59902cc`): - -Use Print data as the primary output action. Only add Send email when the user explicitly requests it. In headless/automated runs (`claude -p`), use Print data only — skip Send email entirely since the recipient cannot be prompted. - -In interactive mode, when the user requests email, **ask for their email address** (with the assistant's input mechanism, or in chat). Never guess or infer it. The `to` field must be a real address — placeholders like `user@example.com` fail at runtime. - -```yaml - send_email: - id: 07413ef9ba7c47bf5a242799f59902cc - properties: - to: - - recipient@company.com # Ask user for real address, or mark as parameterized - subject: "Email subject" - msg: "${data['list_users_action.API_Integration.Custom_Okta.listUsers.body']}" - msg_type: "text" - version_constraint: ~1 -``` +**Print data** has three inputs: `fields` (the CLI reports type `string`; the samples pass a YAML list of `${...}` pills), `text_data` (string — general-purpose), `custom_json` (object only). Use `text_data` for API-integration responses since `body` may be an array; data path `action_key.API_Integration.Custom_{Name}.{Workflow_name}.body` (copy exact paths from the editor's **Workflow data** panel). **Send email** is secondary — add only when explicitly requested, skip in headless runs, and ask for a real `to` address (placeholders fail at runtime). Its inputs are `to` (a list of addresses), `subject`, `msg`, and `msg_type` (`text` or `html`), plus optional `file_attachment` and `skip_workflow_header`. Its ID is the verified one above, so it needs no lookup; `actions view --name "Send email"` also matches similarly named actions such as Gmail - Send Email. Full `send_email` action example: [references/workflow-examples.md](references/workflow-examples.md#send-email-action). ## Variable References -Falcon Fusion SOAR uses [Common Expression Language (CEL)](https://github.com/google/cel-spec/blob/master/doc/langdef.md) for data references. All variable references use `${data['...']}` expression syntax: +Falcon Fusion SOAR uses [Common Expression Language (CEL)](https://github.com/google/cel-spec/blob/master/doc/langdef.md) for data references — all use `${data['...']}` syntax. The `action_key` is the YAML key of the action (e.g. `list_users`), NOT its `id`; an API integration's path segment is `Custom_{name}` (spaces → underscores). Common forms: API body `${data['action_key.API_Integration.Custom_Name.Workflow_name.body']}` (`Workflow_name` is the operation's `x-cs-operation-config.workflow.name` with spaces → underscores; index an array element inside the braces: `${data['…body'][0].field}`), platform output namespaced by action type (`${data['action_key.Device.GetDetails.Platform']}`, `${data['action_key.RTR.PutAndRun.stdout']}`), app AI-agent reply `${data['action_key.response']}` (a `json_with_schema` agent uses `${data['action_key.<schema field>']}` instead), function output `${data['action_key.FaaS.<function>.<handler>.<field>']}` (loop item `…<field>.#.<item field>`), and trigger parameter `${data['param_name']}`. The full table with every form is in [references/cel-expressions.md](references/cel-expressions.md#variable-reference-forms); copy exact paths from the editor's **Workflow data** panel. -| Syntax | Description | -|--------|-------------| -| `${data['action_key.API_Integration.Custom_Name.operationId.body']}` | Response body from an API integration action | -| `${data['action_key.API_Integration.Custom_Name.operationId.body']}[0].field` | Access a field in the first element of an array response | -| `${data['action_key.output.field']}` | Field from a platform action's output | -| `${data['action_key.response']}` | Reply from an app's own AI agent (`ai_agents.<agent name>`); no `.output` segment | -| `${data['param_name']}` | On-demand trigger parameter value (use the parameter name directly, no prefix) | +**CRITICAL:** Do NOT use `$action_name.output.body` — it passes as a literal string and is NOT resolved at runtime. Always use `${data['...']}` expressions. -**CRITICAL:** Do NOT use `$action_name.output.body` — this passes as a literal string and is NOT resolved at runtime. Always use `${data['...']}` expressions. +### CEL Expressions -The `action_key` is the YAML key of the action (e.g., `list_users` from `actions: list_users:`), NOT the action's `id`. The integration name in the variable path is `Custom_{name}` where `{name}` is the `name` field in your `api_integrations` manifest entry (spaces become underscores). Use the **Workflow data** panel in the workflow editor to copy exact data paths — it produces the correct expression when you click a data pill. +Falcon Fusion SOAR supports CEL for data transformations, conditions, and field access. Key patterns: null-safe access with `!= null` (`${data['action.field'] != null ? data['action.field'] : "default"}`), `size()` before indexing a list, and array access with the index INSIDE the braces (`${data['…body'][0]}`, not after). -### CEL Expressions +**`has()` only works on retrieved objects, not data store keys.** `has(data['key'])` fails with `Q0910`; use `data['key'] != null` for keys, or `has(data['var'].field)` to check a field on an already-retrieved object. -Falcon Fusion SOAR supports CEL for data transformations, conditions, and field access. Common patterns: +CrowdStrike adds [custom CEL extensions](https://docs.crowdstrike.com/r/k223d842) (`cs.json.decode()`, `cs.ip.valid()`, `cs.timestamp.parse()`, etc.). For the full pattern catalog, runnable snippets, the `has()` vs `!= null` guide, and extension details, see [references/cel-expressions.md](references/cel-expressions.md). -```yaml -# Null-safe field access — optional pattern (preferred) -"${data[?'action.field'].orValue(\"default\")}" +## Control Flow -# Traditional null check -"${data['action.field'] != null ? data['action.field'] : \"default\"}" +**Loops** iterate over arrays or paginate with cursor-based conditions. They are self-contained sub-workflows at the root `loops:` level; the action before a loop must name it in its `next:` list or the loop deploys but never runs. A loop item is referenced with `${<input>.#}`, and a loop item's field is `...<field>.#.<item field>`. -# Array element access (index goes INSIDE the ${...}, not after it) -"${data['action.API_Integration.Custom_Name.op.body'][0]}" -``` +**Conditions** route with an FQL-style `expression:` or a CEL `cel_expression:`, each with an optional `else:` fallback branch. -**`has()` only works on retrieved objects, not data store keys.** `has(data['key'])` fails with `Q0910`; use `data['key'] != null` for keys, or `has(data['var'].field)` to check a field on an already-retrieved object. +See [references/workflow-examples.md](references/workflow-examples.md#control-flow-loop-and-condition-examples) for full loop (`DeviceLoop` with platform-check routing) and condition examples from production apps. -CrowdStrike adds [custom CEL extensions](https://docs.crowdstrike.com/r/k223d842) (`cs.json.decode()`, `cs.ip.valid()`, `cs.timestamp.parse()`, etc.). For the full pattern catalog, the `has()`/`!= null`/optional decision guide, and extension details, see [references/cel-expressions.md](references/cel-expressions.md). +## Join Resolution & Cyclic References -## Control Flow +Falcon Fusion SOAR builds a DAG. A node inside a parallel branch MUST NOT reach a downstream join **both directly and through a child** — Falcon Fusion SOAR reads that as a cycle and fails the deploy: -**Loops** iterate over arrays or paginate with cursor-based conditions. Loops are self-contained sub-workflows at the root `loops:` level: +❌ `A.next: [Join, B]` + `B.next: [Join]` → `2001 cyclic reference to previously seen node … FROM_B_TO_parallel_A` -```yaml -loops: - DeviceLoop: - for: - input: device_query.Device.query.devices - continue_on_partial_execution: true - sequential: true - trigger: - next: - - get_device_details - actions: - get_device_details: - id: 6265dc947cc2252f74a5f25261ac36a9 - next: - - platform_check - properties: - device_id: "${device_query.Device.query.devices.#}" - version_constraint: ~1 - conditions: - platform_check: - next: - - remediate - expression: get_device_details.Device.GetDetails.Platform:'Windows' - display: - - Platform is Windows - else: - - skip_device -``` +**Fix: linearize.** Make every node whose output a consumer reads a *single-path ancestor* of that consumer — `A → B → Join`. The pill from `A` still reaches `Join` because `A` stays an ancestor. -**Conditions** use FQL-style `expression:` or CEL `cel_expression:` with optional `else:` for fallback routing: +> **Silent variant (no error):** a store/aggregator that reads a node `X`'s output (`${data['X.<field>']}`) when `X` sits on a **diamond fork** resolves **EMPTY** at the join — the pill comes back blank, not an error, which is very hard to diagnose. Same rule, same fix: any node whose output you read must be a single-path ancestor of the reader, never a shared fork. -```yaml -conditions: - has_detection: - next: - - GetDetectionDetails - cel_expression: data['detection_id'] != null && data['detection_id'] != '' - display: - - Detection ID was provided - else: - - PrintSummary -``` +> **A consumer can only read an ancestor's output.** A parallel branch whose `next:` chain never leads to the consumer deploys fine, yet its pill comes back blank there. Make the producer an ancestor of the consumer: add a direct `next:` edge when nothing else the producer feeds also reaches the consumer, and otherwise linearize as above, since a direct edge plus a path through a sibling is the `2001` cycle. -See [references/workflow-examples.md](references/workflow-examples.md) for full loop and condition examples from production apps. +See [Diamond Joins](references/advanced-patterns.md#diamond-joins--the-2001-cyclic-reference) for a worked diamond showing the failure and the linearized rewrite. ## The "0" Gotcha -See [pagination-patterns](references/pagination-patterns.md#the-0-gotcha) for the "0" gotcha and fix pattern. Key point: check for both null and `"0"` in loop conditions. +See [pagination-patterns](references/pagination-patterns.md#the-0-gotcha-in-pagination) for the "0" gotcha and fix pattern. Key point: check for both null and `"0"` in loop conditions. ## Workflow Name Uniqueness -Workflow names must be unique across all apps in the same tenant. If two apps deploy workflows with the same name, the second deploy fails silently or produces an "Unknown error." Use app-specific prefixes when the workflow name is generic. +Workflow names must be unique across all apps installed in a CID. The clash shows up at **install**, not deploy: two apps whose workflows share a name both deploy and release, but installing the second one ends in **Install failed** (the app's state reads `Installation failed`). Use app-specific prefixes when the workflow name is generic. -## NEVER Delete and Recreate Workflows - -> **⚠️ DANGER:** Deleting a workflow and recreating it with the same name causes cascading failures requiring a fresh app to recover. +The exception is `multi_instance: true` at the top of the workflow YAML. With it, the second app installs, and Falcon Fusion SOAR renames its copy with a timestamp suffix (`<name> - 2026-10-29T05:01:07Z`) instead of rejecting it. Set it when several apps created from the same template may be installed in one CID. It doesn't change whether installing creates the workflow, which is still `provision_on_install`. -Removing a workflow from the manifest does NOT delete its server-side artifact. Recreating with the same name → `409 name must be unique for an app`. A once-failed artifact taints the dependency graph (`400 dependent artifact failed`), blocking all further deploys. - -**Instead, update in place** — edit the workflow YAML and redeploy. To re-bind a workflow to a recreated function, update the `id: functions.{name}.{handler}` reference in the YAML. Only delete a workflow if you genuinely no longer need it and won't recreate it with the same name. +## NEVER Delete and Recreate Workflows -## Workflow Sharing +Removing a workflow from the manifest does NOT delete its server-side artifact — recreating with the same name → `409 name must be unique for an app`, and a once-failed artifact taints the dependency graph (`400 dependent artifact failed`), blocking all further deploys. **Update in place instead**: keep the manifest entry and its name, edit the YAML, and redeploy; to re-bind to a recreated function, update the `id: functions.{name}.{handler}` reference. Only delete a workflow if you truly won't recreate it with the same name. If an in-place structural edit hits a 409, use the sticky-409 recipe below. A `400 dependent artifact failed` is different: the failed artifact blocks every later deploy of the app, and recovery means a fresh app (see `ai-agents-development`'s `references/workflow-invocation.md`). -```yaml -workflows: - - name: my-workflow - path: workflows/my-workflow/workflow.yaml - workflow_integration: - id: <generated-id> - disruptive: false - system_action: false # false = available as a Fusion SOAR response action; true = internal app use only -``` +### Sticky-409 recovery (structural change re-provisions and 409s) -> **⚠️ SOAR action visibility:** `system_action: false` = workflow appears as a Fusion SOAR response action (analysts trigger from detections/incidents). `system_action: true` = internal app use only (scheduled sync, helpers). If the user asks for a "SOAR action" or "response action", use `false`. +A structural edit that re-provisions a workflow (a new action, an edited `next`/edge, an added trigger parameter) can fail with `Duplicate workflow name (409)` / `system definition with id … already provisioned on cid …`. **Deleting the Falcon Fusion SOAR workflow does NOT free the name — a used name stays reserved**, so re-deploying the same name keeps 409ing. The reliable escape is to **rename to a brand-new unique name AND strip the `id`** (do both; either one alone still 409s) — the full step-by-step recovery is in [references/advanced-patterns.md](references/advanced-patterns.md#sticky-409-recovery). ## Error Handling -Foundry workflows handle errors through conditional routing and action-level flags — not `onError` blocks or retry middleware. Key mechanisms: `fail_fast_enabled: false` (function actions), `continue_on_partial_execution` (loop blocks), and `conditions:`/`else:` routing. No built-in retry or backoff exists. For the full table, examples, and pagination-polling pattern, see [references/advanced-patterns.md](references/advanced-patterns.md). +Foundry workflows handle errors through conditional routing and action-level flags — not `onError` blocks or retry middleware. Key mechanisms: action-level `continue_on_error: true`, `continue_on_partial_execution` (concurrent loops), and `conditions:`/`else:` on `Workflow.Execution.Errors`. No built-in retry or backoff exists. For the full table, examples, and pagination-polling pattern, see [references/advanced-patterns.md](references/advanced-patterns.md). ## Testing @@ -373,23 +186,18 @@ | Reading alerts/detections: Event Query vs. source-of-truth API | [references/event-query-vs-api.md](references/event-query-vs-api.md) | | Full workflow examples (RTR, investigation) | [references/workflow-examples.md](references/workflow-examples.md) | | Platform action discovery via API | [references/action-discovery.md](references/action-discovery.md) | -| CEL expressions (patterns, has() vs null, extensions) | [references/cel-expressions.md](references/cel-expressions.md) | -| CEL syntax, schemaless queries, dynamic data | [Falcon Fusion SOAR Event Queries: When and How to Go Schemaless](https://www.crowdstrike.com/tech-hub/ng-siem/falcon-fusion-soar-event-queries-when-and-how-to-go-schemaless/) | -| CEL extension functions reference | [Data Transformation Functions](https://docs.crowdstrike.com/r/k223d842) | +| CEL expressions (patterns, has() vs null, extensions, schemaless, extension functions) | [references/cel-expressions.md](references/cel-expressions.md) | | Pagination strategies | [references/pagination-patterns.md](references/pagination-patterns.md) | | HTTP Actions (call REST APIs without an app) | [references/http-actions.md](references/http-actions.md) | | Error handling, HTTP Request actions, parameterized fields, counter-rationalizations | [references/advanced-patterns.md](references/advanced-patterns.md) | ## Use Cases -For real-world implementation patterns, see: -- `use-cases/schemaless-queries.md` — CEL expressions, dynamic data, Event Query configuration -- `use-cases/api-pagination.md` — Pagination strategies in functions and workflows -- `use-cases/custom-soar-actions.md` — Custom Falcon Fusion SOAR actions +Real-world patterns: `use-cases/schemaless-queries.md` (CEL, Event Query config), `use-cases/api-pagination.md` (pagination in functions and workflows), `use-cases/custom-soar-actions.md` (custom Falcon Fusion SOAR actions). ## Reference Implementations -- **[foundry-sample-threat-intel](https://github.com/CrowdStrike/foundry-sample-threat-intel)**: Threat intelligence workflows with pagination -- **[foundry-sample-rapid-response](https://github.com/CrowdStrike/foundry-sample-rapid-response)**: Rapid response automation -- **[foundry-sample-scalable-rtr](https://github.com/CrowdStrike/foundry-sample-scalable-rtr)**: Scalable RTR orchestration -- **[foundry-sample-ngsiem-importer](https://github.com/CrowdStrike/foundry-sample-ngsiem-importer)**: Threat intel import for NG-SIEM +- [foundry-sample-threat-intel](https://github.com/CrowdStrike/foundry-sample-threat-intel) — threat-intel workflows + pagination +- [foundry-sample-rapid-response](https://github.com/CrowdStrike/foundry-sample-rapid-response) — rapid-response automation +- [foundry-sample-scalable-rtr](https://github.com/CrowdStrike/foundry-sample-scalable-rtr) — scalable RTR orchestration +- [foundry-sample-ngsiem-importer](https://github.com/CrowdStrike/foundry-sample-ngsiem-importer) — NG-SIEM threat-intel import
Full technical diff · 3 changed fields
changed /description
"Create and configure Falcon Fusion SOAR workflow YAML for Falcon Foundry apps. TRIGGER when user asks to \"create a workflow\", \"build an automation\", \"configure Fusion SOAR\", \"add an on-demand workflow\", runs `foundry workflows create`, or needs help with Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropriate sub-skill."
"Create and configure Falcon Fusion SOAR workflow YAML for Falcon Foundry apps. TRIGGER when user asks to \"create a workflow\", \"build an automation\", \"configure Falcon Fusion SOAR\", \"add an on-demand workflow\", runs `foundry workflows create`, or needs help with Falcon Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropriate sub-skill."
changed /included_files
[
{
"relative_path": "references/action-discovery.md",
"size_in_bytes": 3322
},
{
"relative_path": "references/advanced-patterns.md",
"size_in_bytes": 8801
},
{
"relative_path": "references/cel-expressions.md",
"size_in_bytes": 2678
},
{
"relative_path": "references/event-query-vs-api.md",
"size_in_bytes": 2605
},
{
"relative_path": "references/http-actions.md",
"size_in_bytes": 7457
},
{
"relative_path": "references/pagination-patterns.md",
"size_in_bytes": 1702
},
{
"relative_path": "references/workflow-examples.md",
"size_in_bytes": 13367
},
{
"relative_path": "scripts/action_search.py",
"size_in_bytes": 3694
}
][
{
"relative_path": "references/action-discovery.md",
"size_in_bytes": 4055
},
{
"relative_path": "references/advanced-patterns.md",
"size_in_bytes": 14479
},
{
"relative_path": "references/cel-expressions.md",
"size_in_bytes": 4838
},
{
"relative_path": "references/event-query-vs-api.md",
"size_in_bytes": 2605
},
{
"relative_path": "references/http-actions.md",
"size_in_bytes": 7457
},
{
"relative_path": "references/pagination-patterns.md",
"size_in_bytes": 1702
},
{
"relative_path": "references/workflow-examples.md",
"size_in_bytes": 18843
},
{
"relative_path": "scripts/action_search.py",
"size_in_bytes": 3694
}
]changed /skill_md_contents
"---\nname: workflows-development\ndescription: Create and configure Falcon Fusion SOAR workflow YAML for Falcon Foundry apps. TRIGGER when user asks to \"create a workflow\", \"build an automation\", \"configure Fusion SOAR\", \"add an on-demand workflow\", runs `foundry workflows create`, or needs help with Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropriate sub-skill.\nversion: 1.6.0\nupdated: 2026-10-01\ntags: [foundry, workflows, fusion-soar, yaml]\nauthor: CrowdStrike\nlicense: MIT\ncompatibility: Claude Code >=1.0\nmetadata:\n category: automation\n---\n\n# Foundry Workflows Development\n\n> Write every workflow definition in Fusion YAML, validate step dependencies before running it, and handle failures with conditional routing and action-level flags ([Error Handling](#error-handling)) — Fusion has no `onError` blocks and no built-in retry.\n\n> **Part of a suite.** If `development-workflow` has not already run, and this is a new app or its first capability, load the `development-workflow` skill first — it owns the CLI prerequisite check, scaffolding order, and manifest coordination.\n\nFalcon Foundry Workflows are YAML-defined automation units executed by the Falcon Fusion engine. They orchestrate multi-step operations across Functions, Collections, CrowdStrike APIs, and RTR sessions with parallelism and state management.\n\n## Prerequisites\n\n- **Workflow Author role** is required in addition to the Falcon Developer role\n- Workflows are YAML templates that can be provisioned as active workflow instances\n- Up to **25 workflows** can be provisioned from a single template\n- Set `provision_on_install: true` to auto-provision when the app is installed\n\n## CLI Scaffolding\n\n```bash\n# Write the workflow YAML to /tmp/ first — the CLI copies it into workflows/\nfoundry workflows create --name \"my-workflow\" --spec /tmp/workflow.yaml --no-prompt\n# After: edit workflows/my-workflow.yml to refine workflow logic\n```\n\n### Discover Available Actions and Triggers\n\n```bash\nfoundry workflows actions view --name \"send email\" --no-prompt # Look up by name\nfoundry workflows actions view --name \"send email\" --no-prompt --output-schema # Output schema\nfoundry workflows actions view --name \"send email\" --no-prompt --mock # Mock output\nfoundry workflows triggers view --no-prompt # List triggers\n```\n\n> **Always use `--no-prompt` on `actions view` and `triggers view`.** As of CLI 2.1.1, multiple matches are listed non-interactively. On older CLIs, partial matches trigger an interactive prompt that fails in headless environments (`Error: no TTY available`). The bundled `action_search.py` is an alternative that works without a manifest directory — see [references/action-discovery.md](references/action-discovery.md).\n\n## Workflow Structure\n\n### Trigger + Actions Format (standard)\n\nThis is the format produced by `foundry workflows create` and used by all production Foundry sample apps:\n\n```yaml\nname: list-okta-users\ndescription: On-demand workflow to list Okta users and print results\nprovision_on_install: true\ntrigger:\n next:\n - list_users\n name: On demand\n type: On demand\nactions:\n list_users:\n id: api_integrations.Okta.listUsers\n next:\n - print_results\n properties: {}\n version_constraint: ~0\n print_results:\n id: aadbf530e35fc452a032f5f8acaaac2a\n properties:\n text_data: \"${data['list_users.API_Integration.Custom_Okta.listUsers.body']}\"\n version_constraint: ~1\noutput_fields: []\n```\n\n**Trigger types:**\n\n| Type | Format |\n|------|--------|\n| On demand | `name: On demand`, `type: On demand` |\n| Scheduled | `event: Schedule`, `schedule: {time_cycle: \"0 */6 * * *\", tz: Etc/UTC}` |\n\n> **⚠️ Null-guard trigger parameters:** When run from the Falcon console, the UI prompts users to fill in parameters. However, when triggered via API or from another workflow, parameters may be empty. Guard defensively:\n>\n> ```yaml\n> conditions:\n> check_param:\n> cel_expression: \"data['param_name'] != null && data['param_name'] != ''\"\n> next:\n> - use_param\n> display:\n> - param_name was provided\n> else:\n> - handle_missing\n> ```\n>\n> Or inline in CEL: `${data[?'param'].orValue(\"default\")}` (preferred) or `${data['param'] != null ? data['param'] : \"default\"}` (traditional)\n\n**Variable syntax in actions:** Use `${data['action_key.path.to.field']}` CEL expressions. See [Variable References](#variable-references) for the full syntax. Do NOT use `$action_name.output.body` — it passes as a literal string and is not resolved.\n\n**Version constraints:** Every action requires `version_constraint`. The `~N` value pins against the activity's declared `semantic_version` field, not its internal iteration count. The rule:\n\n- `~0` = activity has **no** `semantic_version` defined (functions, API integrations, and some platform actions like \"contain device\")\n- `~1` = activity **has** a `semantic_version` (most platform actions: Print data, Send email, Create/Update variable, Get device details, etc.)\n\nUse `foundry workflows actions view --name \"<action>\" --no-prompt` to check. If the activity output shows a semantic_version field, use `~1`. If it does not, use `~0`.\n\n```yaml\nactions:\n my_function:\n id: functions.my-func.process\n properties: {}\n version_constraint: ~0 # no semantic_version defined\n contain_host:\n id: <contain-device-action-id>\n properties:\n device_id: \"${data['trigger.device_id']}\"\n version_constraint: ~0 # no semantic_version defined\n print_results:\n id: aadbf530e35fc452a032f5f8acaaac2a\n properties:\n text_data: \"${data['my_function.output']}\"\n version_constraint: ~1 # has semantic_version\n```\n\n### Manifest Configuration\n\n```yaml\n# manifest.yml\nworkflows:\n - name: my-workflow\n path: workflows/my-workflow/workflow.yaml\n permissions: []\n```\n\nTrigger type and schedule are defined inside the workflow YAML file (via `trigger:` block), not in the manifest. The manifest only declares the workflow name, path, and optional permissions.\n\nFor full RTR multi-host orchestration and investigation pipeline examples, see [references/workflow-examples.md](references/workflow-examples.md).\n\n> RTR scripts are not supported in certified Foundry apps (apps published to the CrowdStrike Store). RTR workflows work in custom/internal apps only.\n\n## Calling Functions from Workflows\n\nFunctions referenced in workflow actions (via `id: functions.{name}.{handler}`) must have `workflow_integration` in the manifest. This binds only at creation time, via `foundry functions create --wf-expose` (plus `--input-schema`/`--output-schema`) — hand-editing `manifest.yml` does not work.\n\nIf a function was created without it, recreate the function. That changes its `workflow_integration.id`, so update the `id: functions.{name}.{handler}` reference in your workflow YAML in place. Do NOT delete and recreate the workflow itself — see the warning below.\n\n**Deploy error if missing:**\n```\n❌ Error: referenced function '{name}' and handler '{handler}' does not have workflow_integration properties defined\n```\n\n**Calling the app's own AI agent**: use `id: ai_agents.<agent name>` (the manifest `name`) with `input` for the prompt and `version_constraint: ~1`; the agent needs `exposure.workflows.system_action: true`. `apps validate` doesn't resolve it, so check the deploy output. See [workflow-invocation](../ai-agents-development/references/workflow-invocation.md).\n\n> **⚠️ Reading Falcon alerts, detections, or incidents? It depends on whether the workflow already holds the object.** *Enriching* a detection the workflow was triggered on (query by its ID, e.g. `Ngsiem.detection.id = ?detectID`) → Event Query action, go schemaless. *Fetching a population you don't have* (\"summarize all high-severity alerts\") → source-of-truth API: a native platform action (e.g. Cases → Search Cases) first, or a FalconPy `Alerts`/`Detects` function when none fits — an Event Query can silently return nothing since NG-SIEM contents are connector-dependent. See [references/event-query-vs-api.md](references/event-query-vs-api.md).\n\n## Calling API Integration Operations\n\n> **💡 Consider HTTP Actions first.** For a simple REST call that doesn't need a custom UI or reusable function, an [HTTP Action](https://www.crowdstrike.com/tech-hub/ng-siem/build-api-integrations-with-falcon-fusion-soar-http-actions/) is faster than an API integration — no app, no OpenAPI spec, no deploy, and 130+ pre-built templates. Use a full API integration when the operation is reused across workflows or paired with functions/UI. See [references/http-actions.md](references/http-actions.md).\n\nWorkflows invoke API integration operations using the `api_integrations.{name}.{operationId}` pattern:\n\n> **⚠️ Always use registered integrations.** If an API integration is declared in `manifest.yml`, the workflow MUST call it via `api_integrations.{name}.{operationId}`. Do NOT use a function that makes raw HTTP calls to the same API with hardcoded credentials or template variables like `{{API_TOKEN}}`. The platform manages authentication, rate limiting, and audit logging through the integration.\n\n```yaml\nactions:\n list_users_action:\n id: api_integrations.Okta.listUsers # {name}.{operationId}\n properties: {}\n version_constraint: ~0\n next:\n - print_data\n\n print_data:\n id: aadbf530e35fc452a032f5f8acaaac2a\n properties:\n text_data: \"${data['list_users_action.API_Integration.Custom_Okta.listUsers.body']}\"\n version_constraint: ~1\n```\n\nThe `{name}` must exactly match the `name` field from the `api_integrations` entry in `manifest.yml`, prefixed with `Custom_`. The platform adds `Custom_` to all API integration names in the variable path. The OpenAPI spec must have a matching `operationId` with a properly structured `x-cs-operation-config`:\n\n```yaml\nx-cs-operation-config:\n workflow:\n name: listUsers\n description: List all users\n expose_to_workflow: true\n system: false\n```\n\nThe `workflow` nesting is required — a flat `expose_to_workflow: true` under `x-cs-operation-config` will not work. Auth scopes for CLI-created artifacts are managed automatically.\n\n## Platform Actions\n\nPlatform actions (send email, log output, create detection) require platform-specific action IDs. These IDs are verified identical across us-1, us-2, and eu-1 clouds:\n\n| Action Name | ID |\n|------------|-----|\n| Create variable | `702d15788dbbffdf0b68d8e2f3599aa4` |\n| Update variable | `6c6eab39063fa3b72d98c82af60deb8a` |\n| Print data | `aadbf530e35fc452a032f5f8acaaac2a` |\n| Sleep | `4f1af1ae4c13dc1e3bcd725f8dc0f63b` |\n| Send email | `07413ef9ba7c47bf5a242799f59902cc` |\n| Request human input - Send email | `d6731c10b24834e2e0f4bd9d390a29c8` |\n| Get device details | `6265dc947cc2252f74a5f25261ac36a9` |\n| Contain device | `bec9fbeb4999d207937854fd56088107` |\n\nFor actions not in this table, use `foundry workflows actions view --name \"...\" --no-prompt` or the API query in [references/action-discovery.md](references/action-discovery.md). There are 9,000+ platform actions available. MUST NOT guess action IDs — use discovery commands.\n\n### Common Action Properties\n\n**Print data** (`aadbf530e35fc452a032f5f8acaaac2a`):\n\nPrint data has three input properties: `fields` (array — dropdown of trigger/workflow metadata), `text_data` (string — general-purpose), and `custom_json` (object only). Use `text_data` for API integration responses since `body` may be an array.\n\n```yaml\n print_data:\n id: aadbf530e35fc452a032f5f8acaaac2a\n properties:\n text_data: \"${data['list_users_action.API_Integration.Custom_Okta.listUsers.body']}\"\n version_constraint: ~1\n```\n\nThe data path follows the pattern: `action_key.API_Integration.Custom_{IntegrationName}.{operationId}.{field}`. The platform adds `Custom_` to all API integration names in the variable path. Use the **Workflow data** panel in the workflow editor to copy the exact path for any field — click the data pill and it copies the correct `${data['...']}` expression to your clipboard.\n\n**Send email** (`07413ef9ba7c47bf5a242799f59902cc`):\n\nUse Print data as the primary output action. Only add Send email when the user explicitly requests it. In headless/automated runs (`claude -p`), use Print data only — skip Send email entirely since the recipient cannot be prompted.\n\nIn interactive mode, when the user requests email, **ask for their email address** (with the assistant's input mechanism, or in chat). Never guess or infer it. The `to` field must be a real address — placeholders like `user@example.com` fail at runtime.\n\n```yaml\n send_email:\n id: 07413ef9ba7c47bf5a242799f59902cc\n properties:\n to:\n - recipient@company.com # Ask user for real address, or mark as parameterized\n subject: \"Email subject\"\n msg: \"${data['list_users_action.API_Integration.Custom_Okta.listUsers.body']}\"\n msg_type: \"text\"\n version_constraint: ~1\n```\n\n## Variable References\n\nFalcon Fusion SOAR uses [Common Expression Language (CEL)](https://github.com/google/cel-spec/blob/master/doc/langdef.md) for data references. All variable references use `${data['...']}` expression syntax:\n\n| Syntax | Description |\n|--------|-------------|\n| `${data['action_key.API_Integration.Custom_Name.operationId.body']}` | Response body from an API integration action |\n| `${data['action_key.API_Integration.Custom_Name.operationId.body']}[0].field` | Access a field in the first element of an array response |\n| `${data['action_key.output.field']}` | Field from a platform action's output |\n| `${data['action_key.response']}` | Reply from an app's own AI agent (`ai_agents.<agent name>`); no `.output` segment |\n| `${data['param_name']}` | On-demand trigger parameter value (use the parameter name directly, no prefix) |\n\n**CRITICAL:** Do NOT use `$action_name.output.body` — this passes as a literal string and is NOT resolved at runtime. Always use `${data['...']}` expressions.\n\nThe `action_key` is the YAML key of the action (e.g., `list_users` from `actions: list_users:`), NOT the action's `id`. The integration name in the variable path is `Custom_{name}` where `{name}` is the `name` field in your `api_integrations` manifest entry (spaces become underscores). Use the **Workflow data** panel in the workflow editor to copy exact data paths — it produces the correct expression when you click a data pill.\n\n### CEL Expressions\n\nFalcon Fusion SOAR supports CEL for data transformations, conditions, and field access. Common patterns:\n\n```yaml\n# Null-safe field access — optional pattern (preferred)\n\"${data[?'action.field'].orValue(\\\"default\\\")}\"\n\n# Traditional null check\n\"${data['action.field'] != null ? data['action.field'] : \\\"default\\\"}\"\n\n# Array element access (index goes INSIDE the ${...}, not after it)\n\"${data['action.API_Integration.Custom_Name.op.body'][0]}\"\n```\n\n**`has()` only works on retrieved objects, not data store keys.** `has(data['key'])` fails with `Q0910`; use `data['key'] != null` for keys, or `has(data['var'].field)` to check a field on an already-retrieved object.\n\nCrowdStrike adds [custom CEL extensions](https://docs.crowdstrike.com/r/k223d842) (`cs.json.decode()`, `cs.ip.valid()`, `cs.timestamp.parse()`, etc.). For the full pattern catalog, the `has()`/`!= null`/optional decision guide, and extension details, see [references/cel-expressions.md](references/cel-expressions.md).\n\n## Control Flow\n\n**Loops** iterate over arrays or paginate with cursor-based conditions. Loops are self-contained sub-workflows at the root `loops:` level:\n\n```yaml\nloops:\n DeviceLoop:\n for:\n input: device_query.Device.query.devices\n continue_on_partial_execution: true\n sequential: true\n trigger:\n next:\n - get_device_details\n actions:\n get_device_details:\n id: 6265dc947cc2252f74a5f25261ac36a9\n next:\n - platform_check\n properties:\n device_id: \"${device_query.Device.query.devices.#}\"\n version_constraint: ~1\n conditions:\n platform_check:\n next:\n - remediate\n expression: get_device_details.Device.GetDetails.Platform:'Windows'\n display:\n - Platform is Windows\n else:\n - skip_device\n```\n\n**Conditions** use FQL-style `expression:` or CEL `cel_expression:` with optional `else:` for fallback routing:\n\n```yaml\nconditions:\n has_detection:\n next:\n - GetDetectionDetails\n cel_expression: data['detection_id'] != null && data['detection_id'] != ''\n display:\n - Detection ID was provided\n else:\n - PrintSummary\n```\n\nSee [references/workflow-examples.md](references/workflow-examples.md) for full loop and condition examples from production apps.\n\n## The \"0\" Gotcha\n\nSee [pagination-patterns](references/pagination-patterns.md#the-0-gotcha) for the \"0\" gotcha and fix pattern. Key point: check for both null and `\"0\"` in loop conditions.\n\n## Workflow Name Uniqueness\n\nWorkflow names must be unique across all apps in the same tenant. If two apps deploy workflows with the same name, the second deploy fails silently or produces an \"Unknown error.\" Use app-specific prefixes when the workflow name is generic.\n\n## NEVER Delete and Recreate Workflows\n\n> **⚠️ DANGER:** Deleting a workflow and recreating it with the same name causes cascading failures requiring a fresh app to recover.\n\nRemoving a workflow from the manifest does NOT delete its server-side artifact. Recreating with the same name → `409 name must be unique for an app`. A once-failed artifact taints the dependency graph (`400 dependent artifact failed`), blocking all further deploys.\n\n**Instead, update in place** — edit the workflow YAML and redeploy. To re-bind a workflow to a recreated function, update the `id: functions.{name}.{handler}` reference in the YAML. Only delete a workflow if you genuinely no longer need it and won't recreate it with the same name.\n\n## Workflow Sharing\n\n```yaml\nworkflows:\n - name: my-workflow\n path: workflows/my-workflow/workflow.yaml\n workflow_integration:\n id: <generated-id>\n disruptive: false\n system_action: false # false = available as a Fusion SOAR response action; true = internal app use only\n```\n\n> **⚠️ SOAR action visibility:** `system_action: false` = workflow appears as a Fusion SOAR response action (analysts trigger from detections/incidents). `system_action: true` = internal app use only (scheduled sync, helpers). If the user asks for a \"SOAR action\" or \"response action\", use `false`.\n\n## Error Handling\n\nFoundry workflows handle errors through conditional routing and action-level flags — not `onError` blocks or retry middleware. Key mechanisms: `fail_fast_enabled: false` (function actions), `continue_on_partial_execution` (loop blocks), and `conditions:`/`else:` routing. No built-in retry or backoff exists. For the full table, examples, and pagination-polling pattern, see [references/advanced-patterns.md](references/advanced-patterns.md).\n\n## Testing\n\nSee [references/advanced-patterns.md](references/advanced-patterns.md) for workflow testing commands (mock triggers, mock actions, execution validation, and `foundry apps validate`).\n\n## Reading Guide\n\n| Task | Reference |\n|------|-----------|\n| Reading alerts/detections: Event Query vs. source-of-truth API | [references/event-query-vs-api.md](references/event-query-vs-api.md) |\n| Full workflow examples (RTR, investigation) | [references/workflow-examples.md](references/workflow-examples.md) |\n| Platform action discovery via API | [references/action-discovery.md](references/action-discovery.md) |\n| CEL expressions (patterns, has() vs null, extensions) | [references/cel-expressions.md](references/cel-expressions.md) |\n| CEL syntax, schemaless queries, dynamic data | [Falcon Fusion SOAR Event Queries: When and How to Go Schemaless](https://www.crowdstrike.com/tech-hub/ng-siem/falcon-fusion-soar-event-queries-when-and-how-to-go-schemaless/) |\n| CEL extension functions reference | [Data Transformation Functions](https://docs.crowdstrike.com/r/k223d842) |\n| Pagination strategies | [references/pagination-patterns.md](references/pagination-patterns.md) |\n| HTTP Actions (call REST APIs without an app) | [references/http-actions.md](references/http-actions.md) |\n| Error handling, HTTP Request actions, parameterized fields, counter-rationalizations | [references/advanced-patterns.md](references/advanced-patterns.md) |\n\n## Use Cases\n\nFor real-world implementation patterns, see:\n- `use-cases/schemaless-queries.md` — CEL expressions, dynamic data, Event Query configuration\n- `use-cases/api-pagination.md` — Pagination strategies in functions and workflows\n- `use-cases/custom-soar-actions.md` — Custom Falcon Fusion SOAR actions\n\n## Reference Implementations\n\n- **[foundry-sample-threat-intel](https://github.com/CrowdStrike/foundry-sample-threat-intel)**: Threat intelligence workflows with pagination\n- **[foundry-sample-rapid-response](https://github.com/CrowdStrike/foundry-sample-rapid-response)**: Rapid response automation\n- **[foundry-sample-scalable-rtr](https://github.com/CrowdStrike/foundry-sample-scalable-rtr)**: Scalable RTR orchestration\n- **[foundry-sample-ngsiem-importer](https://github.com/CrowdStrike/foundry-sample-ngsiem-importer)**: Threat intel import for NG-SIEM\n""---\nname: workflows-development\ndescription: Create and configure Falcon Fusion SOAR workflow YAML for Falcon Foundry apps. TRIGGER when user asks to \"create a workflow\", \"build an automation\", \"configure Falcon Fusion SOAR\", \"add an on-demand workflow\", runs `foundry workflows create`, or needs help with Falcon Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropriate sub-skill.\nversion: 1.7.0\nupdated: 2026-10-30\ntags: [foundry, workflows, fusion-soar, yaml]\nauthor: CrowdStrike\nlicense: MIT\ncompatibility: Claude Code >=1.0\nmetadata:\n category: automation\n---\n\n# Foundry Workflows Development\n\n> Write every workflow definition in Falcon Fusion YAML, validate step dependencies before running it, and handle failures with conditional routing and action-level flags ([Error Handling](#error-handling)) — Fusion has no `onError` blocks and no built-in retry.\n\n> **Part of a suite.** If `development-workflow` has not already run, and this is a new app or its first capability, load the `development-workflow` skill first — it owns the CLI prerequisite check, scaffolding order, and manifest coordination.\n\n## Prerequisites\n\n- **Workflow Author role** is required in addition to the Falcon Developer role\n- Workflows are YAML templates provisioned as active instances (up to **25** per template)\n- **`provision_on_install: true` is REQUIRED** in the workflow YAML — treat it as a per-workflow checklist item, not a footnote. With `true`, installing the app creates the workflow in Falcon Fusion SOAR, turned on. With `false`, the deploy is \"Successful\" and the template is listed in the app's **Logic** section, but installing creates no workflow, so nothing runs until something provisions it (the `/workflows/system-definitions/provision` API). Use `false` deliberately: for a workflow with an action ID you can't verify, which the user finishes in the console (see [Platform Action Fallback Strategy](references/advanced-patterns.md#platform-action-fallback-strategy)), or to let an app install without the credentials a workflow needs, as the sample apps' e2e tests do.\n\n## CLI Scaffolding\n\n```bash\n# Write the workflow YAML to /tmp/ first — the CLI copies it into workflows/\nfoundry workflows create --name \"my-workflow\" --spec /tmp/workflow.yaml --no-prompt\n# After: edit workflows/my-workflow.yml to refine workflow logic\n```\n\n### Discover Available Actions and Triggers\n\n```bash\nfoundry workflows actions view --name \"send email\" --no-prompt # Look up by name\nfoundry workflows actions view --name \"send email\" --no-prompt --output-schema # Output schema\nfoundry workflows actions view --name \"send email\" --no-prompt --mock # Mock output\nfoundry workflows triggers view --no-prompt # List triggers\n```\n\n> **Always use `--no-prompt` on `actions view`/`triggers view`** — without it, multiple or partial matches trigger an interactive prompt that fails in headless environments (`Error: no TTY available`); as of CLI 2.1.1 matches are listed non-interactively. The bundled `action_search.py` works without a manifest directory — see [references/action-discovery.md](references/action-discovery.md).\n\n## Workflow Structure\n\n### Trigger + Actions Format (standard)\n\nThis is the format produced by `foundry workflows create` and used by many Foundry sample apps — a `trigger:` (with `next:` naming the first action) plus an `actions:` map where each action carries an `id`, `properties`, `version_constraint`, and optional `next:`, closing with `output_fields: []`. See [references/workflow-examples.md](references/workflow-examples.md#standard-trigger-actions-format) for the full canonical YAML (on-demand Okta list → print).\n\n**Trigger types:**\n\n| Type | Format |\n|------|--------|\n| On demand | `name: On demand`, `type: On demand` |\n| Scheduled | `event: Schedule`, `schedule: {time_cycle: \"0 */6 * * *\", tz: Etc/UTC}` |\n\n**Trigger parameters** (inputs the console prompts for when an on-demand workflow runs) are a JSON Schema object under `trigger:`, read in actions as `${data['name']}`:\n\n```yaml\ntrigger:\n name: On demand\n type: On demand\n parameters:\n type: object\n properties:\n recipient:\n type: string\n description: Who gets the report\n required:\n - recipient\n```\n\n> **⚠️ Null-guard trigger parameters:** When run from the Falcon console the UI prompts for parameters, but via API or from another workflow they may be empty. Guard with a `conditions:` branch (`cel_expression: data['param'] != null && data['param'] != ''`, routing to a handler via `else:`) or inline in CEL with a ternary: `${data['param'] != null ? data['param'] : \"default\"}`. Full `conditions:` block: [references/cel-expressions.md](references/cel-expressions.md#null-guard-trigger-parameters).\n\n**Variable syntax in actions:** Use `${data['action_key.path.to.field']}` CEL expressions. See [Variable References](#variable-references) for the full syntax. Do NOT use `$action_name.output.body` — it passes as a literal string and is not resolved.\n\n**Version constraints:** Set `version_constraint: ~N` on each action, where `N` is the major version of the activity's declared `semantic_version` (not its iteration count): **`~0`** when the activity has no `semantic_version` (functions, API integrations) or a `0.x` one (Contain device is `0.0.x`); **`~1`** for a `1.x` one (Print data, Send email, Create/Update variable, Get device details). Some samples omit it on function actions. Check with `scripts/action_search.py \"<action>\" --details`, which prints the `semantic_version` and the matching constraint; a worked `~0`/`~1` example is in [references/workflow-examples.md](references/workflow-examples.md#version-constraint-example).\n\n### Manifest Configuration\n\n```yaml\n# manifest.yml\nworkflows:\n - name: my-workflow\n path: workflows/my-workflow.yml\n permissions: []\n```\n\nTrigger type and schedule are defined inside the workflow YAML file (via `trigger:` block), not in the manifest. The manifest only declares the workflow name, path, and optional permissions.\n\n> RTR scripts are not supported in certified Foundry apps (apps published to the CrowdStrike Store). RTR workflows work in custom/internal apps only. For full RTR multi-host orchestration and investigation-pipeline examples, see [references/workflow-examples.md](references/workflow-examples.md).\n\n## Calling Functions from Workflows\n\nFunctions called via `id: functions.{name}.{handler}` must have `workflow_integration` in the manifest. Set it at create time with `foundry functions create --wf-expose` (plus `--input-schema`/`--output-schema`). For a function created without it whose schemas are already set, add the block to the handler in `manifest.yml` (`id: \"\"`, `disruptive`, `system_action`, `tags`, as `--wf-expose` writes it) and redeploy: the deploy fills in the `id` and binds it, including on a function that was already deployed without one. Missing it fails deploy with `referenced function '{name}' and handler '{handler}' does not have workflow_integration properties defined`.\n\n> **⚠️ Every non-empty `properties:` on a function action needs a declared `request_schema`.** A function action passes the handler only the properties its `request_schema` declares; an undeclared property is **silently dropped**, even with `additionalProperties: true`, and no error is raised. Symptom: a function that \"runs fine\" but behaves as if an input was blank. Declare every property the workflow passes. Declare the schema at create time via `foundry functions create … --input-schema` (hand-editing the manifest does not bind it).\n\n**Calling the app's own AI agent**: `id: ai_agents.<agent name>` with `input` (the prompt) and `version_constraint: ~1`; the agent needs `exposure.workflows.system_action: true`, and its reply is read downstream as `${data['action_key.response']}`. `apps validate` doesn't resolve it — check the deploy output. Full walkthrough (aliasing, the `(2018) Action was not found` trap, `json_with_schema` field access) in the `ai-agents-development` skill's `references/workflow-invocation.md`.\n\n> **⚠️ Reading Falcon alerts/detections/incidents? Depends on whether the workflow already holds the object.** *Enriching* one the workflow was triggered on (query by its ID) → Event Query action, schemaless. *Fetching a population you don't have* (\"summarize all high-severity alerts\") → source-of-truth API: a native platform action (e.g. Cases → Search Cases) or a FalconPy `Alerts`/`Detects` function — an Event Query can silently return nothing (NG-SIEM contents are connector-dependent). See [references/event-query-vs-api.md](references/event-query-vs-api.md).\n\n## Calling API Integration Operations\n\n> **💡 Consider HTTP Actions first.** For a one-off REST call (no custom UI or reusable function), an [HTTP Action](https://www.crowdstrike.com/tech-hub/ng-siem/build-api-integrations-with-falcon-fusion-soar-http-actions/) is faster than an API integration — no app, no OpenAPI spec, no deploy, 130+ templates. Use a full API integration when the operation is reused across workflows or paired with functions/UI. See [references/http-actions.md](references/http-actions.md).\n\n> **⚠️ Always call a registered integration** via `api_integrations.{name}.{operationId}` — never a function making raw HTTP calls to the same API with hardcoded creds or `{{API_TOKEN}}`-style templates. The platform owns auth, rate limiting, and audit logging.\n\n`{name}` must match the manifest `api_integrations` entry, prefixed `Custom_` in the variable path (the platform adds it to every integration name). The action `id:` uses the `operationId`, but the next segment of the output path comes from the operation's `x-cs-operation-config.workflow.name` with spaces turned into underscores: an operation with `operationId: Get leavers data` and workflow name `Workday get leavers data` is called as `api_integrations.Workday get leavers data.Get leavers data` and read as `…API_Integration.Custom_Workday_get_leavers_data.Workday_get_leavers_data.body`. Copy the path from the editor's **Workflow data** panel. The OpenAPI `operationId`'s `x-cs-operation-config` must nest the config under a `workflow:` key (`name`, `description`, `expose_to_workflow: true`, `system: false`) — a flat `expose_to_workflow: true` will not work. Auth scopes for CLI-created artifacts are managed automatically. Full action + `x-cs-operation-config` example: [references/workflow-examples.md](references/workflow-examples.md#api-integration-operation-call).\n\n## Platform Actions\n\nPlatform actions (send email, log output, create detection) require platform-specific action IDs, verified identical across us-1, us-2, and eu-1. The two most used are **Print data** `aadbf530e35fc452a032f5f8acaaac2a` and **Send email** `07413ef9ba7c47bf5a242799f59902cc`; the full lookup table (Create/Update variable, Sleep, Get device details, Contain device, Request human input) is in [references/action-discovery.md](references/action-discovery.md#common-platform-action-ids). For any action not listed, use `foundry workflows actions view --name \"...\" --no-prompt`. There are 9,000+ platform actions — MUST NOT guess action IDs; use discovery commands.\n\n### Common Action Properties\n\n**Print data** has three inputs: `fields` (the CLI reports type `string`; the samples pass a YAML list of `${...}` pills), `text_data` (string — general-purpose), `custom_json` (object only). Use `text_data` for API-integration responses since `body` may be an array; data path `action_key.API_Integration.Custom_{Name}.{Workflow_name}.body` (copy exact paths from the editor's **Workflow data** panel). **Send email** is secondary — add only when explicitly requested, skip in headless runs, and ask for a real `to` address (placeholders fail at runtime). Its inputs are `to` (a list of addresses), `subject`, `msg`, and `msg_type` (`text` or `html`), plus optional `file_attachment` and `skip_workflow_header`. Its ID is the verified one above, so it needs no lookup; `actions view --name \"Send email\"` also matches similarly named actions such as Gmail - Send Email. Full `send_email` action example: [references/workflow-examples.md](references/workflow-examples.md#send-email-action).\n\n## Variable References\n\nFalcon Fusion SOAR uses [Common Expression Language (CEL)](https://github.com/google/cel-spec/blob/master/doc/langdef.md) for data references — all use `${data['...']}` syntax. The `action_key` is the YAML key of the action (e.g. `list_users`), NOT its `id`; an API integration's path segment is `Custom_{name}` (spaces → underscores). Common forms: API body `${data['action_key.API_Integration.Custom_Name.Workflow_name.body']}` (`Workflow_name` is the operation's `x-cs-operation-config.workflow.name` with spaces → underscores; index an array element inside the braces: `${data['…body'][0].field}`), platform output namespaced by action type (`${data['action_key.Device.GetDetails.Platform']}`, `${data['action_key.RTR.PutAndRun.stdout']}`), app AI-agent reply `${data['action_key.response']}` (a `json_with_schema` agent uses `${data['action_key.<schema field>']}` instead), function output `${data['action_key.FaaS.<function>.<handler>.<field>']}` (loop item `…<field>.#.<item field>`), and trigger parameter `${data['param_name']}`. The full table with every form is in [references/cel-expressions.md](references/cel-expressions.md#variable-reference-forms); copy exact paths from the editor's **Workflow data** panel.\n\n**CRITICAL:** Do NOT use `$action_name.output.body` — it passes as a literal string and is NOT resolved at runtime. Always use `${data['...']}` expressions.\n\n### CEL Expressions\n\nFalcon Fusion SOAR supports CEL for data transformations, conditions, and field access. Key patterns: null-safe access with `!= null` (`${data['action.field'] != null ? data['action.field'] : \"default\"}`), `size()` before indexing a list, and array access with the index INSIDE the braces (`${data['…body'][0]}`, not after).\n\n**`has()` only works on retrieved objects, not data store keys.** `has(data['key'])` fails with `Q0910`; use `data['key'] != null` for keys, or `has(data['var'].field)` to check a field on an already-retrieved object.\n\nCrowdStrike adds [custom CEL extensions](https://docs.crowdstrike.com/r/k223d842) (`cs.json.decode()`, `cs.ip.valid()`, `cs.timestamp.parse()`, etc.). For the full pattern catalog, runnable snippets, the `has()` vs `!= null` guide, and extension details, see [references/cel-expressions.md](references/cel-expressions.md).\n\n## Control Flow\n\n**Loops** iterate over arrays or paginate with cursor-based conditions. They are self-contained sub-workflows at the root `loops:` level; the action before a loop must name it in its `next:` list or the loop deploys but never runs. A loop item is referenced with `${<input>.#}`, and a loop item's field is `...<field>.#.<item field>`.\n\n**Conditions** route with an FQL-style `expression:` or a CEL `cel_expression:`, each with an optional `else:` fallback branch.\n\nSee [references/workflow-examples.md](references/workflow-examples.md#control-flow-loop-and-condition-examples) for full loop (`DeviceLoop` with platform-check routing) and condition examples from production apps.\n\n## Join Resolution & Cyclic References\n\nFalcon Fusion SOAR builds a DAG. A node inside a parallel branch MUST NOT reach a downstream join **both directly and through a child** — Falcon Fusion SOAR reads that as a cycle and fails the deploy:\n\n❌ `A.next: [Join, B]` + `B.next: [Join]` → `2001 cyclic reference to previously seen node … FROM_B_TO_parallel_A`\n\n**Fix: linearize.** Make every node whose output a consumer reads a *single-path ancestor* of that consumer — `A → B → Join`. The pill from `A` still reaches `Join` because `A` stays an ancestor.\n\n> **Silent variant (no error):** a store/aggregator that reads a node `X`'s output (`${data['X.<field>']}`) when `X` sits on a **diamond fork** resolves **EMPTY** at the join — the pill comes back blank, not an error, which is very hard to diagnose. Same rule, same fix: any node whose output you read must be a single-path ancestor of the reader, never a shared fork.\n\n> **A consumer can only read an ancestor's output.** A parallel branch whose `next:` chain never leads to the consumer deploys fine, yet its pill comes back blank there. Make the producer an ancestor of the consumer: add a direct `next:` edge when nothing else the producer feeds also reaches the consumer, and otherwise linearize as above, since a direct edge plus a path through a sibling is the `2001` cycle.\n\nSee [Diamond Joins](references/advanced-patterns.md#diamond-joins--the-2001-cyclic-reference) for a worked diamond showing the failure and the linearized rewrite.\n\n## The \"0\" Gotcha\n\nSee [pagination-patterns](references/pagination-patterns.md#the-0-gotcha-in-pagination) for the \"0\" gotcha and fix pattern. Key point: check for both null and `\"0\"` in loop conditions.\n\n## Workflow Name Uniqueness\n\nWorkflow names must be unique across all apps installed in a CID. The clash shows up at **install**, not deploy: two apps whose workflows share a name both deploy and release, but installing the second one ends in **Install failed** (the app's state reads `Installation failed`). Use app-specific prefixes when the workflow name is generic.\n\nThe exception is `multi_instance: true` at the top of the workflow YAML. With it, the second app installs, and Falcon Fusion SOAR renames its copy with a timestamp suffix (`<name> - 2026-10-29T05:01:07Z`) instead of rejecting it. Set it when several apps created from the same template may be installed in one CID. It doesn't change whether installing creates the workflow, which is still `provision_on_install`.\n\n## NEVER Delete and Recreate Workflows\n\nRemoving a workflow from the manifest does NOT delete its server-side artifact — recreating with the same name → `409 name must be unique for an app`, and a once-failed artifact taints the dependency graph (`400 dependent artifact failed`), blocking all further deploys. **Update in place instead**: keep the manifest entry and its name, edit the YAML, and redeploy; to re-bind to a recreated function, update the `id: functions.{name}.{handler}` reference. Only delete a workflow if you truly won't recreate it with the same name. If an in-place structural edit hits a 409, use the sticky-409 recipe below. A `400 dependent artifact failed` is different: the failed artifact blocks every later deploy of the app, and recovery means a fresh app (see `ai-agents-development`'s `references/workflow-invocation.md`).\n\n### Sticky-409 recovery (structural change re-provisions and 409s)\n\nA structural edit that re-provisions a workflow (a new action, an edited `next`/edge, an added trigger parameter) can fail with `Duplicate workflow name (409)` / `system definition with id … already provisioned on cid …`. **Deleting the Falcon Fusion SOAR workflow does NOT free the name — a used name stays reserved**, so re-deploying the same name keeps 409ing. The reliable escape is to **rename to a brand-new unique name AND strip the `id`** (do both; either one alone still 409s) — the full step-by-step recovery is in [references/advanced-patterns.md](references/advanced-patterns.md#sticky-409-recovery).\n\n## Error Handling\n\nFoundry workflows handle errors through conditional routing and action-level flags — not `onError` blocks or retry middleware. Key mechanisms: action-level `continue_on_error: true`, `continue_on_partial_execution` (concurrent loops), and `conditions:`/`else:` on `Workflow.Execution.Errors`. No built-in retry or backoff exists. For the full table, examples, and pagination-polling pattern, see [references/advanced-patterns.md](references/advanced-patterns.md).\n\n## Testing\n\nSee [references/advanced-patterns.md](references/advanced-patterns.md) for workflow testing commands (mock triggers, mock actions, execution validation, and `foundry apps validate`).\n\n## Reading Guide\n\n| Task | Reference |\n|------|-----------|\n| Reading alerts/detections: Event Query vs. source-of-truth API | [references/event-query-vs-api.md](references/event-query-vs-api.md) |\n| Full workflow examples (RTR, investigation) | [references/workflow-examples.md](references/workflow-examples.md) |\n| Platform action discovery via API | [references/action-discovery.md](references/action-discovery.md) |\n| CEL expressions (patterns, has() vs null, extensions, schemaless, extension functions) | [references/cel-expressions.md](references/cel-expressions.md) |\n| Pagination strategies | [references/pagination-patterns.md](references/pagination-patterns.md) |\n| HTTP Actions (call REST APIs without an app) | [references/http-actions.md](references/http-actions.md) |\n| Error handling, HTTP Request actions, parameterized fields, counter-rationalizations | [references/advanced-patterns.md](references/advanced-patterns.md) |\n\n## Use Cases\n\nReal-world patterns: `use-cases/schemaless-queries.md` (CEL, Event Query config), `use-cases/api-pagination.md` (pagination in functions and workflows), `use-cases/custom-soar-actions.md` (custom Falcon Fusion SOAR actions).\n\n## Reference Implementations\n\n- [foundry-sample-threat-intel](https://github.com/CrowdStrike/foundry-sample-threat-intel) — threat-intel workflows + pagination\n- [foundry-sample-rapid-response](https://github.com/CrowdStrike/foundry-sample-rapid-response) — rapid-response automation\n- [foundry-sample-scalable-rtr](https://github.com/CrowdStrike/foundry-sample-scalable-rtr) — scalable RTR orchestration\n- [foundry-sample-ngsiem-importer](https://github.com/CrowdStrike/foundry-sample-ngsiem-importer) — NG-SIEM threat-intel import\n"Full snapshot data
{
"description": "Create and configure Falcon Fusion SOAR workflow YAML for Falcon Foundry apps. TRIGGER when user asks to \"create a workflow\", \"build an automation\", \"configure Falcon Fusion SOAR\", \"add an on-demand workflow\", runs `foundry workflows create`, or needs help with Falcon Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropriate sub-skill.",
"included_files": [
{
"relative_path": "references/action-discovery.md",
"size_in_bytes": 4055
},
{
"relative_path": "references/advanced-patterns.md",
"size_in_bytes": 14479
},
{
"relative_path": "references/cel-expressions.md",
"size_in_bytes": 4838
},
{
"relative_path": "references/event-query-vs-api.md",
"size_in_bytes": 2605
},
{
"relative_path": "references/http-actions.md",
"size_in_bytes": 7457
},
{
"relative_path": "references/pagination-patterns.md",
"size_in_bytes": 1702
},
{
"relative_path": "references/workflow-examples.md",
"size_in_bytes": 18843
},
{
"relative_path": "scripts/action_search.py",
"size_in_bytes": 3694
}
],
"name": "workflows-development",
"skill_md_contents": "---\nname: workflows-development\ndescription: Create and configure Falcon Fusion SOAR workflow YAML for Falcon Foundry apps. TRIGGER when user asks to \"create a workflow\", \"build an automation\", \"configure Falcon Fusion SOAR\", \"add an on-demand workflow\", runs `foundry workflows create`, or needs help with Falcon Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropriate sub-skill.\nversion: 1.7.0\nupdated: 2026-10-30\ntags: [foundry, workflows, fusion-soar, yaml]\nauthor: CrowdStrike\nlicense: MIT\ncompatibility: Claude Code >=1.0\nmetadata:\n category: automation\n---\n\n# Foundry Workflows Development\n\n> Write every workflow definition in Falcon Fusion YAML, validate step dependencies before running it, and handle failures with conditional routing and action-level flags ([Error Handling](#error-handling)) — Fusion has no `onError` blocks and no built-in retry.\n\n> **Part of a suite.** If `development-workflow` has not already run, and this is a new app or its first capability, load the `development-workflow` skill first — it owns the CLI prerequisite check, scaffolding order, and manifest coordination.\n\n## Prerequisites\n\n- **Workflow Author role** is required in addition to the Falcon Developer role\n- Workflows are YAML templates provisioned as active instances (up to **25** per template)\n- **`provision_on_install: true` is REQUIRED** in the workflow YAML — treat it as a per-workflow checklist item, not a footnote. With `true`, installing the app creates the workflow in Falcon Fusion SOAR, turned on. With `false`, the deploy is \"Successful\" and the template is listed in the app's **Logic** section, but installing creates no workflow, so nothing runs until something provisions it (the `/workflows/system-definitions/provision` API). Use `false` deliberately: for a workflow with an action ID you can't verify, which the user finishes in the console (see [Platform Action Fallback Strategy](references/advanced-patterns.md#platform-action-fallback-strategy)), or to let an app install without the credentials a workflow needs, as the sample apps' e2e tests do.\n\n## CLI Scaffolding\n\n```bash\n# Write the workflow YAML to /tmp/ first — the CLI copies it into workflows/\nfoundry workflows create --name \"my-workflow\" --spec /tmp/workflow.yaml --no-prompt\n# After: edit workflows/my-workflow.yml to refine workflow logic\n```\n\n### Discover Available Actions and Triggers\n\n```bash\nfoundry workflows actions view --name \"send email\" --no-prompt # Look up by name\nfoundry workflows actions view --name \"send email\" --no-prompt --output-schema # Output schema\nfoundry workflows actions view --name \"send email\" --no-prompt --mock # Mock output\nfoundry workflows triggers view --no-prompt # List triggers\n```\n\n> **Always use `--no-prompt` on `actions view`/`triggers view`** — without it, multiple or partial matches trigger an interactive prompt that fails in headless environments (`Error: no TTY available`); as of CLI 2.1.1 matches are listed non-interactively. The bundled `action_search.py` works without a manifest directory — see [references/action-discovery.md](references/action-discovery.md).\n\n## Workflow Structure\n\n### Trigger + Actions Format (standard)\n\nThis is the format produced by `foundry workflows create` and used by many Foundry sample apps — a `trigger:` (with `next:` naming the first action) plus an `actions:` map where each action carries an `id`, `properties`, `version_constraint`, and optional `next:`, closing with `output_fields: []`. See [references/workflow-examples.md](references/workflow-examples.md#standard-trigger-actions-format) for the full canonical YAML (on-demand Okta list → print).\n\n**Trigger types:**\n\n| Type | Format |\n|------|--------|\n| On demand | `name: On demand`, `type: On demand` |\n| Scheduled | `event: Schedule`, `schedule: {time_cycle: \"0 */6 * * *\", tz: Etc/UTC}` |\n\n**Trigger parameters** (inputs the console prompts for when an on-demand workflow runs) are a JSON Schema object under `trigger:`, read in actions as `${data['name']}`:\n\n```yaml\ntrigger:\n name: On demand\n type: On demand\n parameters:\n type: object\n properties:\n recipient:\n type: string\n description: Who gets the report\n required:\n - recipient\n```\n\n> **⚠️ Null-guard trigger parameters:** When run from the Falcon console the UI prompts for parameters, but via API or from another workflow they may be empty. Guard with a `conditions:` branch (`cel_expression: data['param'] != null && data['param'] != ''`, routing to a handler via `else:`) or inline in CEL with a ternary: `${data['param'] != null ? data['param'] : \"default\"}`. Full `conditions:` block: [references/cel-expressions.md](references/cel-expressions.md#null-guard-trigger-parameters).\n\n**Variable syntax in actions:** Use `${data['action_key.path.to.field']}` CEL expressions. See [Variable References](#variable-references) for the full syntax. Do NOT use `$action_name.output.body` — it passes as a literal string and is not resolved.\n\n**Version constraints:** Set `version_constraint: ~N` on each action, where `N` is the major version of the activity's declared `semantic_version` (not its iteration count): **`~0`** when the activity has no `semantic_version` (functions, API integrations) or a `0.x` one (Contain device is `0.0.x`); **`~1`** for a `1.x` one (Print data, Send email, Create/Update variable, Get device details). Some samples omit it on function actions. Check with `scripts/action_search.py \"<action>\" --details`, which prints the `semantic_version` and the matching constraint; a worked `~0`/`~1` example is in [references/workflow-examples.md](references/workflow-examples.md#version-constraint-example).\n\n### Manifest Configuration\n\n```yaml\n# manifest.yml\nworkflows:\n - name: my-workflow\n path: workflows/my-workflow.yml\n permissions: []\n```\n\nTrigger type and schedule are defined inside the workflow YAML file (via `trigger:` block), not in the manifest. The manifest only declares the workflow name, path, and optional permissions.\n\n> RTR scripts are not supported in certified Foundry apps (apps published to the CrowdStrike Store). RTR workflows work in custom/internal apps only. For full RTR multi-host orchestration and investigation-pipeline examples, see [references/workflow-examples.md](references/workflow-examples.md).\n\n## Calling Functions from Workflows\n\nFunctions called via `id: functions.{name}.{handler}` must have `workflow_integration` in the manifest. Set it at create time with `foundry functions create --wf-expose` (plus `--input-schema`/`--output-schema`). For a function created without it whose schemas are already set, add the block to the handler in `manifest.yml` (`id: \"\"`, `disruptive`, `system_action`, `tags`, as `--wf-expose` writes it) and redeploy: the deploy fills in the `id` and binds it, including on a function that was already deployed without one. Missing it fails deploy with `referenced function '{name}' and handler '{handler}' does not have workflow_integration properties defined`.\n\n> **⚠️ Every non-empty `properties:` on a function action needs a declared `request_schema`.** A function action passes the handler only the properties its `request_schema` declares; an undeclared property is **silently dropped**, even with `additionalProperties: true`, and no error is raised. Symptom: a function that \"runs fine\" but behaves as if an input was blank. Declare every property the workflow passes. Declare the schema at create time via `foundry functions create … --input-schema` (hand-editing the manifest does not bind it).\n\n**Calling the app's own AI agent**: `id: ai_agents.<agent name>` with `input` (the prompt) and `version_constraint: ~1`; the agent needs `exposure.workflows.system_action: true`, and its reply is read downstream as `${data['action_key.response']}`. `apps validate` doesn't resolve it — check the deploy output. Full walkthrough (aliasing, the `(2018) Action was not found` trap, `json_with_schema` field access) in the `ai-agents-development` skill's `references/workflow-invocation.md`.\n\n> **⚠️ Reading Falcon alerts/detections/incidents? Depends on whether the workflow already holds the object.** *Enriching* one the workflow was triggered on (query by its ID) → Event Query action, schemaless. *Fetching a population you don't have* (\"summarize all high-severity alerts\") → source-of-truth API: a native platform action (e.g. Cases → Search Cases) or a FalconPy `Alerts`/`Detects` function — an Event Query can silently return nothing (NG-SIEM contents are connector-dependent). See [references/event-query-vs-api.md](references/event-query-vs-api.md).\n\n## Calling API Integration Operations\n\n> **💡 Consider HTTP Actions first.** For a one-off REST call (no custom UI or reusable function), an [HTTP Action](https://www.crowdstrike.com/tech-hub/ng-siem/build-api-integrations-with-falcon-fusion-soar-http-actions/) is faster than an API integration — no app, no OpenAPI spec, no deploy, 130+ templates. Use a full API integration when the operation is reused across workflows or paired with functions/UI. See [references/http-actions.md](references/http-actions.md).\n\n> **⚠️ Always call a registered integration** via `api_integrations.{name}.{operationId}` — never a function making raw HTTP calls to the same API with hardcoded creds or `{{API_TOKEN}}`-style templates. The platform owns auth, rate limiting, and audit logging.\n\n`{name}` must match the manifest `api_integrations` entry, prefixed `Custom_` in the variable path (the platform adds it to every integration name). The action `id:` uses the `operationId`, but the next segment of the output path comes from the operation's `x-cs-operation-config.workflow.name` with spaces turned into underscores: an operation with `operationId: Get leavers data` and workflow name `Workday get leavers data` is called as `api_integrations.Workday get leavers data.Get leavers data` and read as `…API_Integration.Custom_Workday_get_leavers_data.Workday_get_leavers_data.body`. Copy the path from the editor's **Workflow data** panel. The OpenAPI `operationId`'s `x-cs-operation-config` must nest the config under a `workflow:` key (`name`, `description`, `expose_to_workflow: true`, `system: false`) — a flat `expose_to_workflow: true` will not work. Auth scopes for CLI-created artifacts are managed automatically. Full action + `x-cs-operation-config` example: [references/workflow-examples.md](references/workflow-examples.md#api-integration-operation-call).\n\n## Platform Actions\n\nPlatform actions (send email, log output, create detection) require platform-specific action IDs, verified identical across us-1, us-2, and eu-1. The two most used are **Print data** `aadbf530e35fc452a032f5f8acaaac2a` and **Send email** `07413ef9ba7c47bf5a242799f59902cc`; the full lookup table (Create/Update variable, Sleep, Get device details, Contain device, Request human input) is in [references/action-discovery.md](references/action-discovery.md#common-platform-action-ids). For any action not listed, use `foundry workflows actions view --name \"...\" --no-prompt`. There are 9,000+ platform actions — MUST NOT guess action IDs; use discovery commands.\n\n### Common Action Properties\n\n**Print data** has three inputs: `fields` (the CLI reports type `string`; the samples pass a YAML list of `${...}` pills), `text_data` (string — general-purpose), `custom_json` (object only). Use `text_data` for API-integration responses since `body` may be an array; data path `action_key.API_Integration.Custom_{Name}.{Workflow_name}.body` (copy exact paths from the editor's **Workflow data** panel). **Send email** is secondary — add only when explicitly requested, skip in headless runs, and ask for a real `to` address (placeholders fail at runtime). Its inputs are `to` (a list of addresses), `subject`, `msg`, and `msg_type` (`text` or `html`), plus optional `file_attachment` and `skip_workflow_header`. Its ID is the verified one above, so it needs no lookup; `actions view --name \"Send email\"` also matches similarly named actions such as Gmail - Send Email. Full `send_email` action example: [references/workflow-examples.md](references/workflow-examples.md#send-email-action).\n\n## Variable References\n\nFalcon Fusion SOAR uses [Common Expression Language (CEL)](https://github.com/google/cel-spec/blob/master/doc/langdef.md) for data references — all use `${data['...']}` syntax. The `action_key` is the YAML key of the action (e.g. `list_users`), NOT its `id`; an API integration's path segment is `Custom_{name}` (spaces → underscores). Common forms: API body `${data['action_key.API_Integration.Custom_Name.Workflow_name.body']}` (`Workflow_name` is the operation's `x-cs-operation-config.workflow.name` with spaces → underscores; index an array element inside the braces: `${data['…body'][0].field}`), platform output namespaced by action type (`${data['action_key.Device.GetDetails.Platform']}`, `${data['action_key.RTR.PutAndRun.stdout']}`), app AI-agent reply `${data['action_key.response']}` (a `json_with_schema` agent uses `${data['action_key.<schema field>']}` instead), function output `${data['action_key.FaaS.<function>.<handler>.<field>']}` (loop item `…<field>.#.<item field>`), and trigger parameter `${data['param_name']}`. The full table with every form is in [references/cel-expressions.md](references/cel-expressions.md#variable-reference-forms); copy exact paths from the editor's **Workflow data** panel.\n\n**CRITICAL:** Do NOT use `$action_name.output.body` — it passes as a literal string and is NOT resolved at runtime. Always use `${data['...']}` expressions.\n\n### CEL Expressions\n\nFalcon Fusion SOAR supports CEL for data transformations, conditions, and field access. Key patterns: null-safe access with `!= null` (`${data['action.field'] != null ? data['action.field'] : \"default\"}`), `size()` before indexing a list, and array access with the index INSIDE the braces (`${data['…body'][0]}`, not after).\n\n**`has()` only works on retrieved objects, not data store keys.** `has(data['key'])` fails with `Q0910`; use `data['key'] != null` for keys, or `has(data['var'].field)` to check a field on an already-retrieved object.\n\nCrowdStrike adds [custom CEL extensions](https://docs.crowdstrike.com/r/k223d842) (`cs.json.decode()`, `cs.ip.valid()`, `cs.timestamp.parse()`, etc.). For the full pattern catalog, runnable snippets, the `has()` vs `!= null` guide, and extension details, see [references/cel-expressions.md](references/cel-expressions.md).\n\n## Control Flow\n\n**Loops** iterate over arrays or paginate with cursor-based conditions. They are self-contained sub-workflows at the root `loops:` level; the action before a loop must name it in its `next:` list or the loop deploys but never runs. A loop item is referenced with `${<input>.#}`, and a loop item's field is `...<field>.#.<item field>`.\n\n**Conditions** route with an FQL-style `expression:` or a CEL `cel_expression:`, each with an optional `else:` fallback branch.\n\nSee [references/workflow-examples.md](references/workflow-examples.md#control-flow-loop-and-condition-examples) for full loop (`DeviceLoop` with platform-check routing) and condition examples from production apps.\n\n## Join Resolution & Cyclic References\n\nFalcon Fusion SOAR builds a DAG. A node inside a parallel branch MUST NOT reach a downstream join **both directly and through a child** — Falcon Fusion SOAR reads that as a cycle and fails the deploy:\n\n❌ `A.next: [Join, B]` + `B.next: [Join]` → `2001 cyclic reference to previously seen node … FROM_B_TO_parallel_A`\n\n**Fix: linearize.** Make every node whose output a consumer reads a *single-path ancestor* of that consumer — `A → B → Join`. The pill from `A` still reaches `Join` because `A` stays an ancestor.\n\n> **Silent variant (no error):** a store/aggregator that reads a node `X`'s output (`${data['X.<field>']}`) when `X` sits on a **diamond fork** resolves **EMPTY** at the join — the pill comes back blank, not an error, which is very hard to diagnose. Same rule, same fix: any node whose output you read must be a single-path ancestor of the reader, never a shared fork.\n\n> **A consumer can only read an ancestor's output.** A parallel branch whose `next:` chain never leads to the consumer deploys fine, yet its pill comes back blank there. Make the producer an ancestor of the consumer: add a direct `next:` edge when nothing else the producer feeds also reaches the consumer, and otherwise linearize as above, since a direct edge plus a path through a sibling is the `2001` cycle.\n\nSee [Diamond Joins](references/advanced-patterns.md#diamond-joins--the-2001-cyclic-reference) for a worked diamond showing the failure and the linearized rewrite.\n\n## The \"0\" Gotcha\n\nSee [pagination-patterns](references/pagination-patterns.md#the-0-gotcha-in-pagination) for the \"0\" gotcha and fix pattern. Key point: check for both null and `\"0\"` in loop conditions.\n\n## Workflow Name Uniqueness\n\nWorkflow names must be unique across all apps installed in a CID. The clash shows up at **install**, not deploy: two apps whose workflows share a name both deploy and release, but installing the second one ends in **Install failed** (the app's state reads `Installation failed`). Use app-specific prefixes when the workflow name is generic.\n\nThe exception is `multi_instance: true` at the top of the workflow YAML. With it, the second app installs, and Falcon Fusion SOAR renames its copy with a timestamp suffix (`<name> - 2026-10-29T05:01:07Z`) instead of rejecting it. Set it when several apps created from the same template may be installed in one CID. It doesn't change whether installing creates the workflow, which is still `provision_on_install`.\n\n## NEVER Delete and Recreate Workflows\n\nRemoving a workflow from the manifest does NOT delete its server-side artifact — recreating with the same name → `409 name must be unique for an app`, and a once-failed artifact taints the dependency graph (`400 dependent artifact failed`), blocking all further deploys. **Update in place instead**: keep the manifest entry and its name, edit the YAML, and redeploy; to re-bind to a recreated function, update the `id: functions.{name}.{handler}` reference. Only delete a workflow if you truly won't recreate it with the same name. If an in-place structural edit hits a 409, use the sticky-409 recipe below. A `400 dependent artifact failed` is different: the failed artifact blocks every later deploy of the app, and recovery means a fresh app (see `ai-agents-development`'s `references/workflow-invocation.md`).\n\n### Sticky-409 recovery (structural change re-provisions and 409s)\n\nA structural edit that re-provisions a workflow (a new action, an edited `next`/edge, an added trigger parameter) can fail with `Duplicate workflow name (409)` / `system definition with id … already provisioned on cid …`. **Deleting the Falcon Fusion SOAR workflow does NOT free the name — a used name stays reserved**, so re-deploying the same name keeps 409ing. The reliable escape is to **rename to a brand-new unique name AND strip the `id`** (do both; either one alone still 409s) — the full step-by-step recovery is in [references/advanced-patterns.md](references/advanced-patterns.md#sticky-409-recovery).\n\n## Error Handling\n\nFoundry workflows handle errors through conditional routing and action-level flags — not `onError` blocks or retry middleware. Key mechanisms: action-level `continue_on_error: true`, `continue_on_partial_execution` (concurrent loops), and `conditions:`/`else:` on `Workflow.Execution.Errors`. No built-in retry or backoff exists. For the full table, examples, and pagination-polling pattern, see [references/advanced-patterns.md](references/advanced-patterns.md).\n\n## Testing\n\nSee [references/advanced-patterns.md](references/advanced-patterns.md) for workflow testing commands (mock triggers, mock actions, execution validation, and `foundry apps validate`).\n\n## Reading Guide\n\n| Task | Reference |\n|------|-----------|\n| Reading alerts/detections: Event Query vs. source-of-truth API | [references/event-query-vs-api.md](references/event-query-vs-api.md) |\n| Full workflow examples (RTR, investigation) | [references/workflow-examples.md](references/workflow-examples.md) |\n| Platform action discovery via API | [references/action-discovery.md](references/action-discovery.md) |\n| CEL expressions (patterns, has() vs null, extensions, schemaless, extension functions) | [references/cel-expressions.md](references/cel-expressions.md) |\n| Pagination strategies | [references/pagination-patterns.md](references/pagination-patterns.md) |\n| HTTP Actions (call REST APIs without an app) | [references/http-actions.md](references/http-actions.md) |\n| Error handling, HTTP Request actions, parameterized fields, counter-rationalizations | [references/advanced-patterns.md](references/advanced-patterns.md) |\n\n## Use Cases\n\nReal-world patterns: `use-cases/schemaless-queries.md` (CEL, Event Query config), `use-cases/api-pagination.md` (pagination in functions and workflows), `use-cases/custom-soar-actions.md` (custom Falcon Fusion SOAR actions).\n\n## Reference Implementations\n\n- [foundry-sample-threat-intel](https://github.com/CrowdStrike/foundry-sample-threat-intel) — threat-intel workflows + pagination\n- [foundry-sample-rapid-response](https://github.com/CrowdStrike/foundry-sample-rapid-response) — rapid-response automation\n- [foundry-sample-scalable-rtr](https://github.com/CrowdStrike/foundry-sample-scalable-rtr) — scalable RTR orchestration\n- [foundry-sample-ngsiem-importer](https://github.com/CrowdStrike/foundry-sample-ngsiem-importer) — NG-SIEM threat-intel import\n"
}SHA-256 of public snapshot: ee30ce8498e85e5540588a9207853b6816be1ec3a56bd72f802533dde2753904