smithery/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.

Installation

$ npx skills add smithery/treasure-data --skill connector-config

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/treasure-data · top by installs.

npx skills add smithery/treasure-data

Browse all from smithery/treasure-data

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,787 B
  • docs SUMMARY.md 247 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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 (salesforcemarketingcloud_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