Visual Crossing to MotherDuck integration

Connect Visual Crossing to MotherDuck and automatically sync your application data. Weld extracts data from Visual Crossing, loads it into MotherDuck, and lets you transform the data using SQL or dbt, no custom scripts required.

4.8 on G2
Visual CrossingSource
WeldWeld
MotherDuckWarehouse
Weld · New sync
Visual CrossingSourceVisual CrossingConnected
Tables to sync

Your own tables, picked when you set up the sync.

  • Extract
  • Load
  • Keep in sync
MotherDuckDestinationMotherDuckReady
visual_crossing schema
  • visual_crossing.Synced
  • visual_crossing.Syncing
  • visual_crossing.Synced
  • visual_crossing.Synced

Trusted by data and AI teams

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up Visual Crossing to MotherDuck in Weld.
In the app, with the API or an agent.

Weld · New Visual Crossing sync
Visual CrossingNew connectionVisual CrossingAuthorised
Connection namevisual_crossing
AuthorizeOpens Visual Crossing to grant read access
Use cases

Why sync Visual Crossing to MotherDuck?
Ready for analysis.

Centralizing your Visual Crossing data in MotherDuck lets you join it with other data sources for cross-platform analytics and deeper insights.

Build reliable dashboards and reports by querying Visual Crossing data directly in MotherDuck using SQL or your preferred BI tool.

  • Centralized data warehouse

    Bring Visual Crossing data into MotherDuck alongside other sources to create a single source of truth for your organization.

  • Automated reporting

    Replace manual exports and spreadsheet-based reporting with automated pipelines from Visual Crossing to MotherDuck. Connect BI tools like Looker, Metabase, or Power BI.

Data

What data can you sync?
From Visual Crossing to MotherDuck.

Weld syncs the objects the Visual Crossing connector exposes into MotherDuck, and you choose which tables and fields to include. The connector's docs list what is available.

    Weld MCP server

    Ask your agent.
    It queries MotherDuck for you.

    Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Visual Crossing context, finds the tables it needs and runs the query in MotherDuck.

    Claude CodeOpus 5
    >

    Which Visual Crossing tables do we have in MotherDuck, and which is the largest?

    Looking up what Weld has synced from Visual Crossing.

    ●weld·search_available_references
    ⎿raw.visual_crossing.*
    tables, columns and freshness
    ●weld·get_reference_schema
    ⎿columns, types and nullability
    ●weld·run_query
    ⎿select count(*) from {{raw.visual_crossing.…}}
    submitted
    ●weld·get_query_status
    ⎿DONE
    ●weld·get_query_result
    ⎿rows returned
    ✓Answered from Visual Crossing data in MotherDuck
    >Ask about your Visual Crossing data
    Under the hood

    Technical considerations.
    What to expect.

    Incremental syncing
    Weld uses incremental syncing where supported by the Visual Crossing API, loading only new and updated records to minimize data transfer and warehouse costs.
    Schema handling
    Weld automatically manages schema changes. If Visual Crossing adds new fields, they're detected and added to the corresponding MotherDuck tables.
    Data freshness
    Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
    Security
    All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
    FAQ

    Common questions.
    About Visual Crossing to MotherDuck.

    Still have a question?
    Talk to us

    Start syncing Visual Crossing to MotherDuck.

    Set up your Visual Crossing data pipeline in minutes. No credit card required. Free for 14 days.

    Visual CrossingSource
    WeldWeld
    MotherDuckWarehouse