September 2026

New connectors

Claimlane

Claimlane is now available as an ELT source, syncing 10 tables (27 including subtables) covering retailers, suppliers, B2B and B2C claim tickets, and raw data exports for warranty and returns management.

Connections authenticate with an API key. Because most endpoints are scoped to a retailer or supplier organization, the connection settings include an organization picker; leaving it empty syncs every organization the key can see.

Walmart

Walmart Marketplace is now available as an ELT source, syncing 57 tables covering the catalogue, inventory, orders, returns, feed submissions, pricing, payments, shipping settings, WFS inbound shipments, and listing quality.

Connections authenticate with the Client ID and Client Secret from Seller Center's API Key Management page (Walmart's Direct API integration). Weld exchanges them for a short-lived access token on every run, so there is nothing to re-authorize as long as the key pair stays valid.

Catalogue and inventory

Orders and returns

Feeds, pricing and payments

Shipping settings and inbound shipments

Listing quality

Explore Walmart documentation →

QRFY

QRFY is now available as an ELT source, syncing QR codes, folders, and scan analytics from the QR code generator platform.

Connections authenticate with an API key.

New features

Orchestration overview: sorting, contents, and a disabled filter

The orchestration overview now sorts workflows alphabetically, treating leading numbers numerically so "2. Klaviyo Sync" sorts before "10. Shopify Sync" instead of after it. Each workflow's card also gets a line summarizing what it contains, for example how many models, source tables, reverse ETL syncs, and webhooks it runs. A new toggle lets you hide disabled workflows, and only appears once you have at least one disabled workflow to hide.

Capture deletes (Beta)

This feature is in Beta. A table's full syncs can now keep the rows the source stops returning, instead of the sync silently removing them from your destination table. Turn on Capture deletes in the table's settings menu, just above History tables, and rows the source drops on the next full sync are marked with _weld_deleted_at rather than deleted — so they stay queryable for auditing or point-in-time analysis. A row that comes back is unmarked again. See Capture deletes for the full guide.

Within Google Ads, it is the predefined dimension reports (e.g. campaign, ad_group, ad) and their bidding strategy and criterion substreams that qualify, so a full sync marks the entities the account no longer returns instead of dropping the rows. Time-based reports keep reconciling per report window, and custom reports built from your own query are unaffected.

Your data warehouse has to support it too. Capture deletes works on BigQuery, Snowflake, Redshift, Postgres, MSSQL, and MotherDuck.

Configuring syncs programmatically? The same setting is soft_delete_enabled on a stream over the Weld Connect API and the MCP server, and both capabilities are readable before you turn it on: soft_delete_supported per stream from get_elt_sync_available_streams, and the data warehouse's support from GET /data_warehouse or the MCP get_account tool.

Error markers in the SQL editor

A failed preview now places an error marker on the line the warehouse blamed, right in the SQL editor, instead of only showing its message in the bottom pane. The marker follows the SQL as you keep editing: changing the line it blamed clears the marker, editing elsewhere repositions it, and undoing back to the failing query brings it back.

The marker spans the whole line rather than a single column, since the warehouse counts columns into the SQL Weld actually sent, after Weld's own {{tag}} references have already been substituted.

The editor can now also validate your SQL against the warehouse while you type, marking the offending line before you ever run the query. Validation is debounced to a typing pause and cached by SQL text, and runs the query as a free dry run or EXPLAIN rather than actually executing it. If the SQL is valid, any leftover marker from an earlier failed run is cleared.

Explanations for quarantined syncs

When a sync stream is quarantined, Weld now generates a plain-language explanation of what happened, instead of showing the raw underlying error. The card also lists suggested next steps as controls you can act on directly, such as re-authenticating a connection, adjusting a sync's incremental settings, reducing its sync frequency, or contacting support with the affected table already noted.

When the cause is on Weld's side rather than something in your setup, the card states that no action is needed instead of suggesting self-serve fixes that would not help.

Identifier casing for Snowflake

Snowflake resolves an unquoted identifier to its upper-case form, and Weld quotes every name it writes, so a table created as "orders" could only ever be queried quoted. You can now have Weld create schemas, tables and columns in upper case instead:

select id from hubspot.orders

Turn on Create tables and columns in upper case under Advanced when you connect Snowflake, or later on the Data Warehouse settings page, to set the default for new syncs. Individual syncs can override it next to the destination schema name when you create them. Over the API, send identifier_casing on POST /elt_syncs and read or change the default on /data_warehouse.

Read more about identifier casing →

Connector updates

Recurly: New discount column on invoices

Recurly's invoice table gains a discount column, alongside the existing discounted column.

Recurly: Coupon redemption table

Recurly gains a coupon_redemption table. Since there is no site-level endpoint for redemptions, it is fetched per account and covers both account-level and subscription-level redemptions. A new invoice_coupon_redemption subtable on invoice links each redemption to the invoices it discounted.

NetSuite: Five new SuiteAnalytics tables

NetSuite gains five tables from its SuiteQL / SuiteAnalytics schema, which have no REST record behind them. transactionaccountingline carries the GL account and debit/credit per transaction line, which is what a trial balance, P&L, or balance sheet is built from. entity and item are the union tables behind the per-type records (customer, vendor, inventory item, and the rest). accounttype and accountingperiodfiscalcalendars are small reference tables with no modified date, so they sync in full on every run.

QuickBooks: Bill enrichment, linked transactions, and expense line fixes

QuickBooks's bill table now carries its doc_number, private_note, home_balance, exchange_rate, vendor address, and last-modified-by and sales term references. A new bill_linked_txn table syncs the transactions linked to a bill, such as its payment, and both expense line subtables gain their own linked transaction subtable for the same purpose at the line level.

Expense lines also gain a project_ref column, and bill_account_based_expense_line rows now include their amount, which the line's schema previously left out.

QuickBooks: Vendor credit table

QuickBooks now has a vendor_credit table, syncing vendor credits with their account details, tax details, and metadata. Line items sync into vendor_credit_account_based_expense_line and vendor_credit_item_based_expense_line subtables, matching how expense lines are already split for other QuickBooks transaction tables.

Criteo: Ad sets, campaign IDs on statistics reports, and a wider primary key

Criteo now has an adset table. Ad sets sit between campaigns and ads.

The adset_statistics_daily_report table is new, and the existing ad_statistics_daily_report table now also carries adset_id and campaign_id on every row, so ads, ad sets, and campaigns can all be connected without a join. Requesting these id columns also brings back their names, so all three statistics reports now expose readable campaign, adset, and ad name columns alongside the ids.

Traede: Delivery and invoice addresses on orders

The order stream now syncs the delivery and invoice addresses as delivery_* and shop_* columns (12 fields each: name, attention line, address lines, zip, city, region, country, email, telephone, VAT, and EAN). shop is Traede's include name for the invoice address; Weld surfaces it as shop_* to stay true to the API rather than colliding with a real invoice include if Traede ever adds one.

These addresses were previously unavailable: the earlier attempt used include names (addresses, delivery_address) that Traede's supported v10 API rejects with a 422. All fields are nullable, since not every order carries a full address.

HiBob: Employment history stream, richer employee data, and custom fields

HiBob now has an employee_employment_history stream, syncing every employment change (contract, working pattern, salary type, and similar terms) with its own effective date, instead of only the employee's current employment terms.

The employee stream itself now syncs many more fields: employment terms (contract, type, FTE, weekly hours, salary pay type, FLSA code, working pattern), lifecycle status and termination details, work address, salary, and personal fields such as pronouns and nationality, each alongside HiBob's human-readable version of the value where one exists.

Custom fields, whose ids are tenant-specific (e.g. about.custom.field_1724744461985), now sync as dedicated employee_custom_fields and employee_payroll_custom_column tables keyed by field name instead of being dropped. Employment history entries carry their own custom columns the same way, via employee_employment_history_custom_field.

The time_off stream now also requests up to two years into the future and includes pending requests, so upcoming and pending time off show up alongside approved past and current entries.

Fortnox: Vouchers stream is now incremental

The vouchers stream now syncs incrementally based on each voucher's last modified date, instead of doing a full resync of all financial years on every run. Updates to existing vouchers are picked up without re-reading the full history each time.

Cargoson: Bookings stream

Cargoson now supports a bookings stream. Instead of paginating Cargoson's booking API, the stream reads the booking references you already hold in a table or view in your data warehouse and resolves each distinct reference against the Cargoson API, including its packages, containers, package units, and ADR (dangerous goods) rows.

Select the table or view holding your booking references, and the column with the booking id, in the connection settings. Only distinct, non-empty values are looked up.

Platform

Weld Connect API and MCP server: primary key columns can no longer be excluded

The Weld Connect API and MCP server now reject any stream whose excluded_columns includes one of its primary key columns, the same way the app already does.

GET /elt_syncs/{id}/available_source_streams (and get_elt_sync_available_streams) now also return a primary_keys field so you can see which columns to avoid excluding before adding a stream.

History tables now seed from existing data when enabled

Turning on the history table for a stream that was already syncing previously only captured changes from that point forward. Any row whose last change predated enabling history had no entry in __history at all, and stayed missing until it happened to change again, so a slow-moving table could leave most of its rows absent from history.

__history is now seeded from the current main table the first time it's created, so the full existing dataset is captured immediately instead of waiting on future changes. This also repairs a __history table that was deleted after being created. Supported for BigQuery, Snowflake, Postgres, Redshift, MSSQL, ClickHouse and MotherDuck destinations.

ClickHouse: Incremental schema changes

Schema changes on a ClickHouse destination no longer force a full resync of the table. Weld now applies the same schema changes incrementally as it does for other destinations: adding a subschema, adding or removing a field (nullable or required), and changing a field's nullability in either direction.

Type changes still require a full resync, since ClickHouse can only convert between compatible column types and doing so rewrites the whole table.

Bug fixes

• Fixed Google Drive syncs configured via the API or MCP server (rather than the Weld app's connection form) failing to resolve their folder, which caused get_elt_sync_available_streams and add_elt_sync_source_streams to return 500 errors instead of listing or adding streams. The folder is now resolved consistently across stream listing, streaming, and schema generation, and the settings API now offers a list of real Google Drive folders to choose from instead of requiring a folder ID.