How do I install the Connector Config skill?

Run npx skillmds add treasure-data/connector-config in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Connector Config safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Connector Config?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Connector Config free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Connector Config?

treasure-data (@treasure-data) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Connector Config by treasure-data — Agent Skill

Name: Connector Config
Rating: 4.2 (5 reviews)
Author: treasure-data

Connector Config

Writes connector_config for segment/journey activations using `tdx connection schema <type>` to discover available fields. Use when configuring activations - always run schema command first to see connector-specific fields.

File contents

tdx Connector Config

Configure connector_config for activations by discovering fields with tdx connection schema.

Key Commands

# List connections (shows type and name)
tdx connection list

# Discover connector_config fields (ALWAYS run this first)
tdx connection schema <connector_type>   # Pass the TYPE (not connection name)

# List all connector types
tdx connection types

Schema vs Settings: schema shows connector_config fields for activations. settings shows credentials for creating connections.

Workflow

tdx connection list                                    # 1. Find connection type
tdx connection schema salesforce_marketing_cloud_v2    # 2. Get schema fields
# 3. Write connector_config → 4. tdx sg push --dry-run

Common Connector Types

Salesforce Marketing Cloud (salesforce_marketing_cloud_v2)

connector_config:
  de_name: CustomerSegment           # Data Extension name (requires primary key)
  shared_data_extension: false
  data_operation: upsert             # upsert | replace
  # For creating new DE:
  create_new_de: true
  folder_path: Segments/Marketing
  primary_column: email
  is_sendable: true
  sendable_rule: Email Address       # "Subscriber Key" | "Email Address"
  sendable_column: email

Salesforce CRM (sfdc_v2)

connector_config:
  object: Contact
  mode: update                       # append | truncate | update
  unique: email                      # Key field (when mode=update)
  upsert: true

AWS S3 (s3_v2)

connector_config:
  bucket: my-bucket
  path: exports/segments/data.csv
  format: csv                        # csv | tsv | jsonl
  compression: gz                    # none | gz

BigQuery (bigquery_v2)

connector_config:
  project: my-gcp-project
  dataset: marketing
  table: segments
  mode: APPEND                       # APPEND | REPLACE | REPLACE_BACKUP | TRUNCATE
  auto_create_table: true

Treasure Data (treasure_data)

connector_config:
  database_name: marketing_db
  table_name: exported_segments
  mode: append                       # append | replace

Conditional Fields

Schema output shows when fields apply:

unique: Key [text]
  Show when: mode=["update"]

Only include unique when mode is update.

Related Skills

activation - Activation structure (connection, schedule, columns, notifications)
segment - Segment rule syntax
journey - Journey structure and activation steps

---name: connector-configdescription: Writes connector_config for segment/journey activations using `tdx connection schema <type>` to discover available fields. Use when configuring activations - always run schema command first to see connector-specific fields.---# tdx Connector ConfigConfigure `connector_config` for activations by discovering fields with `tdx connection schema`.## Key Commands```bash# List connections (shows type and name)tdx connection list# Discover connector_config fields (ALWAYS run this first)tdx connection schema <connector_type> # Pass the TYPE (not connection name)# List all connector typestdx connection types```**Schema vs Settings**: `schema` shows `connector_config` fields for activations. `settings` shows credentials for creating connections.## Workflow```bashtdx connection list # 1. Find connection typetdx connection schema salesforce_marketing_cloud_v2 # 2. Get schema fields# 3. Write connector_config → 4. tdx sg push --dry-run```## Common Connector Types### Salesforce Marketing Cloud (salesforce_marketing_cloud_v2)```yamlconnector_config: de_name: CustomerSegment # Data Extension name (requires primary key) shared_data_extension: false data_operation: upsert # upsert | replace # For creating new DE: create_new_de: true folder_path: Segments/Marketing primary_column: email is_sendable: true sendable_rule: Email Address # "Subscriber Key" | "Email Address" sendable_column: email```### Salesforce CRM (sfdc_v2)```yamlconnector_config: object: Contact mode: update # append | truncate | update unique: email # Key field (when mode=update) upsert: true```### AWS S3 (s3_v2)```yamlconnector_config: bucket: my-bucket path: exports/segments/data.csv format: csv # csv | tsv | jsonl compression: gz # none | gz```### BigQuery (bigquery_v2)```yamlconnector_config: project: my-gcp-project dataset: marketing table: segments mode: APPEND # APPEND | REPLACE | REPLACE_BACKUP | TRUNCATE auto_create_table: true```### Treasure Data (treasure_data)```yamlconnector_config: database_name: marketing_db table_name: exported_segments mode: append # append | replace```## Conditional FieldsSchema output shows when fields apply:```unique: Key [text] Show when: mode=["update"]```Only include `unique` when `mode` is `update`.## Related Skills- **activation** - Activation structure (connection, schedule, columns, notifications)- **segment** - Segment rule syntax- **journey** - Journey structure and activation steps

Frequently asked questions