QRFY
QRFY is a QR code platform for creating, designing and tracking dynamic QR codes — from simple URL codes to menus, vCards, coupons and app download codes. With Weld you can sync your QR codes, folders and scan analytics into your data warehouse and combine them with the rest of your marketing data to report on scan performance across campaigns, locations and devices.
Features
| Feature name | Supported | |
|---|---|---|
| Column Hashing | True | Column level |
| Blocking | True | Column level |
| Incremental | True | |
| Custom data | False | |
| History | True | |
| ReSync | True | Table level |
| Templates | False |
Data Schema
Setup Guide - ELT
Prerequisites
- You need a QRFY plan that includes API access — the API is not available on QRFY's Free plan.
- You need a QRFY API key. Weld only reads from QRFY — it never writes back.
Step 1 - Create your QRFY API key
- Sign in to your account on qrfy.com.
- Open your account settings and go to the API Key section to generate an API key.
- Copy the key.
Step 2 - Create the connection
- In the Weld app, navigate to Connections and click + New Connection.
- Search for QRFY and select it.
- Enter the destination schema name of your choice. This name is used to identify the connection in future syncs.
- Paste your API key.
- Click Connect to validate the key and establish the connection.
Step 3 - Data To Sync
Select the tables you wish to include in the sync. You can view the schema, remove columns or hash sensitive information.
The connector exposes three streams:
qr— every QR code in your account, with its name, type, short URL, folder and scan counters. The type-specific content and the visual design of each code are broken out into separate tables:qr_style— the design configuration of each code (colors, logo, margins). Deeply nested design blocks (shape,corners,frame) are kept as JSON columns.qr_data_<type>— one table per QR code type (url,url_static,pdf,vcard,vcard_plus,business,menu,coupon,event,feedback,images,video,mp3,app,link_list,social,sms,email,text,wifi,whatsapp,barcode). Each QR code produces a row only in the table matching its type, joined toqrviaqr_id.- Repeated fields inside a type's content — such as a link list's links or a vCard's phone numbers — are broken out further into
qr_data_<type>_<field>tables.
folder— the folders your QR codes are organized into.analytics— the detailed scan report: one row per scan with the date, country, city, operating system and scanned/destination URLs.
Step 4 - Configure sync
- Select how often you would like the data to sync.
- For the
analyticstable, choose a start date to limit how far back the initial sync goes. - Provide a unique destination table name.
Weld will take over from here and commence syncing data from your QRFY account.
How syncing works
Full and incremental streams
qr (with all of its substreams) and folder are refreshed in full on every run — QRFY's API does not expose a way to fetch only recently modified codes.
analytics syncs incrementally: the first run backfills scans from your chosen start date (or the last two years if you don't pick one), and each subsequent run only asks QRFY for scans since the previous successful sync.
Joining scans to QR codes
Rows in analytics do not carry a QR code id. Instead, each scan row includes scan_url — the short-code URL of the scanned QR code — which you can join to the corresponding field on the qr table to attribute scans to a specific code.