connector-config

Connector_config generation uses `tdx connection schema` to discover available fields from your connection, then maps those fields to activation configurations for platforms like Salesforce Marketing Cloud, CRM, AWS S3, BigQuery, and Treasure Data. Run schema discovery first, then write and validate the connector_config with a dry-run before applying.

Supported fields vary by connector type: Salesforce Marketing Cloud uses de_name and shared_data_extension; CRM uses data_operation and create_new_de; S3 uses bucket, path, format, and compression; BigQuery uses project, dataset, table, and auto_create_table. Schema discovery reveals which fields are available for your specific connection.

Yes, running `tdx connection schema <connector_type>` is required before writing connector_config. Schema discovery identifies available fields in your connection, which you then apply to activation configurations. This step ensures your field mapping is valid for the target connector.

After writing connector_config, use `push --dry-run` to validate the configuration without applying changes. This preview catches field mapping errors and configuration issues before they affect your segment or journey activations.

Yes, connector_config applies to both segment and journey activations across supported connectors including Salesforce Marketing Cloud, CRM, AWS S3, BigQuery, and Treasure Data. The same schema discovery and field-mapping workflow supports both activation types.