Storepoint to MotherDuck integration

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

4.8 on G2
StorepointSource
WeldWeld
MotherDuckWarehouse
Weld · New sync
StorepointSourceStorepointConnected
Tables to sync
  • location_custom_field4 cols
  • location22 cols
  • location_tag3 cols
  • Extract
  • Load
  • Keep in sync
MotherDuckDestinationMotherDuckReady
storepoint schema
  • storepoint.location_custom_fieldSynced
  • storepoint.locationSyncing
  • storepoint.location_tagSynced
Storepoint tables
4
fields, typed
33
relationships kept
1
agent context included
MCP

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 Storepoint to MotherDuck in Weld.
In the app, with the API or an agent.

Weld · New Storepoint sync
StorepointNew connectionStorepointAuthorised
Connection namestorepoint
AuthorizeOpens Storepoint to grant read access
Use cases

Why sync Storepoint to MotherDuck?
Ready for analysis.

Centralizing your Storepoint 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 Storepoint data directly in MotherDuck using SQL or your preferred BI tool.

  • Centralized data warehouse

    Bring Storepoint 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 Storepoint to MotherDuck. Connect BI tools like Looker, Metabase, or Power BI.

Schema

What data can you sync?
Every Storepoint table, keys intact.

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

Open the schema explorer
All 4 tables
  • location_custom_field
  • location
  • location_tag
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 Storepoint context, finds the tables it needs and runs the query in MotherDuck.

Claude CodeOpus 5
>

How many location_custom_field rows do we have per location? Use our Storepoint data in MotherDuck.

Reading the Storepoint context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.storepoint.location_custom_field
raw.storepoint.location
+ 2 more Storepoint tables
●weld·get_reference_schema
⎿location_custom_field · 4 columns
joins location on location_id
●weld·run_query
⎿select j.id, count(*) from {{raw.storepoint.location_custom_field}} l
join {{raw.storepoint.location}} j on l.location_id = j.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Storepoint data in MotherDuck
>Ask about your Storepoint data
Under the hood

Technical considerations.
What to expect.

Incremental syncing
Weld uses incremental syncing where supported by the Storepoint API, loading only new and updated records to minimize data transfer and warehouse costs.
Schema handling
Weld automatically manages schema changes. If Storepoint 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 Storepoint to MotherDuck.

Start syncing Storepoint to MotherDuck.

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

StorepointSource
WeldWeld
MotherDuckWarehouse