# Incremental Activation Standalone Workflow Incremental Activation is a Beta release. For more information, contact your Customer Success Representative. This page explains how to use Incremental Activation as a standalone workflow without Audience Studio. This allows you to perform delta exports directly from any TD table on a scheduled basis. ## Overview When running Incremental Activation as a standalone workflow, you can: - Export delta changes from any TD table (not just segment data) - Schedule periodic delta exports to your destination - Process data outside of Audience Studio's activation framework **Key difference**: All parameters must be explicitly configured in the workflow, as they are not automatically populated by Audience Studio. ## Required Additional Parameters In standalone mode, you must configure these additional parameters: | Parameter | Description | Example | | --- | --- | --- | | `activation_actions_db` | Source TD database | `"my_database"` | | `activation_actions_table` | Source table name | `"customer_profiles"` | | `result_connection_name` | Connector authentication name | `"my_snowflake_connection"` | | `result_connection_settings` | Connector configuration object | See examples below | ## Standalone Workflow Template ```yaml timezone: "UTC" _export: params: # API endpoint - change based on your TD site api_endpoint: "https://integrations-gateway.us01.treasuredata.com" # Unique identifier column id_key: "customer_id" # Columns to check for changes delta_keys: ["email", "status", "tier"] # Delta mappings activation_mappings: [ { "delta_status": "new", "connector_field": "mode", "connector_field_value": "append" }, { "delta_status": "updated", "connector_field": "mode", "connector_field_value": "append" } ] # REQUIRED: Standalone mode parameters activation_actions_db: "my_database" activation_actions_table: "customer_profiles" result_connection_name: "my_snowflake_connection" result_connection_settings: type: "snowflake" database: "MARKETING_DB" schema: "PUBLIC" table: "CUSTOMER_SEGMENTS" mode: "append" # Fetch and execute incremental activation workflow +fetch_incremental_activation_wf: http_call>: "${params.api_endpoint}/integration_workflow/workflows/incremental_activation/fetch" method: POST headers: - Authorization: ${secret:td.apikey} - Content-Type: "application/json" content_type_override: application/x-yaml content: | { "database": "${params.activation_actions_db}", "source_table": "${params.activation_actions_table}", "id_key": "${params.id_key}", "delta_keys": ${JSON.stringify(params.delta_keys)}, "activation_mappings": ${JSON.stringify(params.activation_mappings)}, "result_connection_settings": ${JSON.stringify(params.result_connection_settings)}, "result_connection_name": "${params.result_connection_name}" } retry: true ``` ## Connector Configuration Examples ### Snowflake ```yaml result_connection_settings: type: "snowflake" database: "MARKETING_DB" schema: "PUBLIC" table: "CUSTOMER_SEGMENTS" mode: "append" ``` ### MySQL ```yaml result_connection_settings: type: "mysql" database: "marketing" table: "customer_segments" mode: "append" ``` ### PostgreSQL ```yaml result_connection_settings: type: "postgresql" database: "marketing" schema: "public" table: "customer_segments" mode: "append" ``` ### Google Sheets ```yaml result_connection_settings: type: "google_sheets" spreadsheet_id: "1ABC...xyz" sheet_name: "Customer List" mode: "replace" ``` ## Setup Steps 1. **Create a new user-defined workflow** in TD Data Workbench > Workflows 2. **Copy and paste** the standalone template above 3. **Configure all required parameters**: - Set `api_endpoint` for your TD site - Set `id_key` to your unique identifier column - Set `delta_keys` to columns you want to track - Set `activation_actions_db` and `activation_actions_table` - Configure `result_connection_settings` for your destination - Set `result_connection_name` to your authentication 4. **Save the workflow** 5. **Run manually** or **schedule** the workflow ## Scheduling To run the workflow on a schedule, add a schedule configuration: ```yaml schedule: daily>: 02:00:00 # Run daily at 2 AM UTC timezone: "UTC" _export: params: # ... rest of configuration ``` ## Use Cases ### Daily Customer Profile Sync Export only changed customer profiles to your data warehouse every night: ```yaml schedule: daily>: 01:00:00 _export: params: api_endpoint: "https://integrations-gateway.us01.treasuredata.com" id_key: "customer_id" delta_keys: ["email", "phone", "address", "tier"] activation_actions_db: "customer_data" activation_actions_table: "unified_profiles" # ... connector settings ``` ### Hourly Product Catalog Updates Sync product catalog changes to an e-commerce platform: ```yaml schedule: hourly>: 00 _export: params: api_endpoint: "https://integrations-gateway.us01.treasuredata.com" id_key: "product_id" delta_keys: ["price", "stock_quantity", "availability"] activation_actions_db: "product_catalog" activation_actions_table: "products" # ... connector settings ``` ## Differences from Activation Action Mode | Aspect | Activation Action Mode | Standalone Mode | | --- | --- | --- | | Triggered by | Audience Studio segment activation | Workflow schedule or manual run | | Data source | Segment syndication table (automatic) | Any TD table (manual configuration) | | Auto-populated params | Yes (`activation_actions_db`, `activation_actions_table`, connector settings) | No (all parameters must be configured) | | Use case | Marketing activations from segments | Scheduled delta exports from any table | ## Next Steps - [Incremental Activation Overview](/products/customer-data-platform/audience-studio/activation/incremental-activation-overview) - [Incremental Activation Parameters](/products/customer-data-platform/audience-studio/activation/incremental-activation-parameters) - [Workflow Templates](/products/customer-data-platform/audience-studio/activation/incremental-activation-workflow-templates) ## Related Topics - [Configure Incremental Activation](/products/customer-data-platform/audience-studio/activation/configure-incremental-activation) - [Creating and Editing a Workflow](/products/customer-data-platform/data-workbench/workflows/getting-started-with-treasure-workflow)