Cargoson to Databricks integration

Connect Cargoson to Databricks and automatically sync your application data.

Get started free Cargoson connector

Cargoson

Data source

Authenticating...

Ready to connect

CONNECTOR SOURCE

Cargoson to Databricks

Connect Cargoson to Databricks and automatically sync your application data. Weld extracts Records, Users, and Events from Cargoson, loads them into Databricks, and lets you transform the data using SQL or dbt, no custom scripts required.

Everything you need to get started

Cargoson

Setup guide Connector page

Databricks

Setup guide Connector page

Weld Connect API

Set up programmatically

Use the Weld Connect REST API to create Cargoson connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

Explore Weld Connect API reference

POST/elt_syncs

# Create a Cargoson ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "cargoson",
    "destination_schema_name": "cargoson_data",
    "sync_interval": "0 * * * *"
  }'
▌

FAQs

How do I sync Cargoson data to Databricks?

Sign up for Weld, connect Cargoson as a source and Databricks as a destination. Weld handles the extraction, loading, and lets you transform data using SQL or dbt.

What Cargoson data can I sync to Databricks?

You can sync Records, Users, and Events. The available objects depend on your Cargoson account permissions and configuration.

How often does Weld sync data from Cargoson?

Sync frequency depends on your Weld plan. Schedules range from every 5 minutes to daily intervals. Each sync processes only new and changed data.

Can I transform Cargoson data before it lands in Databricks?

Yes. Weld supports SQL-based transformations in the platform and integrates with dbt Cloud. You can clean, join, and model your data before analysis.

Is the Cargoson to Databricks integration secure?

Yes. Weld encrypts all data in transit and at rest, is SOC 2 Type II certified, and supports IP whitelisting. Credentials are stored encrypted and never logged.