How to Connect Cardly to Google Sheets (4 Methods Compared)

The Problem With Getting Sheet Data In and Out of Cardly

You have a Google Sheet full of recipient data — names, addresses, personalised messages, template IDs, campaign tags. You need it in Cardly so cards actually go out, or you need Cardly's order data back in the sheet so finance can reconcile the spend.

Cardly is good at turning spreadsheet rows into personalised physical cards at scale. But there's a gap between "data is in a sheet" and "Cardly has it." The default flow is to export a CSV, reformat it to match Cardly's column expectations, upload it through the contact import UI, and then cross your fingers that nothing got truncated at row 200.

Below are the four common ways teams handle this. Only the last one scales.

Method 1: Manual Copy-Paste

The default for smaller sends. You open the Google Sheet, copy the relevant rows, switch to Cardly, and either paste into their import UI or recreate the contacts by hand. For a list of twelve VIP clients, this is manageable.

Thirty recipients in, you've already caught two address typos that didn't surface until you tried to map the postcode field. By the fiftieth row, you're copy-pasting the same city name into a field that should have auto-filled. By the hundredth, you've lost track of which rows you've already processed.

Weekly campaign cadences are what turn this from an annoyance into a full afternoon.

Method 2: Zapier or Make

Both platforms have Cardly connector options. You can wire up a trigger that fires when a new row lands in a sheet, calls the Cardly API, and creates a contact or submits a card order.

Before you go further: do you know what a webhook trigger is? A field mapping interface? An API key and where to paste it? A filter step? If those aren't second nature, this isn't your fastest path — Method 4 will get you there without the detour.

If you're still reading: the setup is genuinely workable. You authenticate both sides, choose your trigger (new row, row updated, or on a schedule), map every column to its Cardly field, and test with a live row. It works.

But a trigger-per-row automation is not a bulk operation.

If you need to push 200 recipients in one go, that's 200 separate trigger fires, 200 API calls, and a task log that becomes unreadable the moment one row returns an address validation error and the rest silently continue.

You probably just need to upload the list and move on. You probably have no idea how to configure a Zap that batches rows, handles partial failures gracefully, and retries only the ones that errored. And you really shouldn't have to. So you ask whoever on your team builds automations — and now it's their ticket, not your send.

Cost scales too. Once you're chaining a filter step, an error handler, and a follow-up notification, you're well past the base tier.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, the best option for repeatable spreadsheet ↔ Cardly workflows was a category of add-ons that let you configure column mappings, save a template, and push or pull data on demand. You picked your range, tagged your Cardly fields, saved the config, and ran it.

That was a real step up from copy-paste. The output was consistent, the config was reusable, and you didn't have to reformat your CSV every time.

But you were still responsible for the field mapping, the conditional logic about which rows to include, the dedup check, the column order. The add-on moved the data through, but every decision about which data and in what shape was still yours to make. And when Cardly updated a field name or you added a new column to the sheet, your saved config broke until someone went in and updated it by hand.

This is the previous generation. It worked, but it demanded a lot of the person running it.

The Easy Way: Using SheetXAI in Google Sheets

There is a different way entirely. SheetXAI is an AI agent that lives inside your Google Sheet. It reads the sheet, understands what you're looking at, and through its built-in Cardly integration it can push to or pull from Cardly for you. No import template to configure, no Zap to debug, no manual reformatting. You just ask.

Example 1: Bulk generate card previews before a send

For every row in the "Recipients" tab (columns A–E: Name, Address Line 1, City, Postcode, Country), generate a Cardly preview using template ID T-001 and write each preview URL to column F.

Each preview URL lands in the corresponding row. You can scan the whole list in the sheet before placing the order.

Example 2: Pull last quarter's order data for reconciliation

Pull all Cardly orders placed between January 1 and March 31 into this sheet — include order ID, recipient name, template used, cost, and delivery status in separate columns.

The pattern: instead of exporting from Cardly and reformatting in the sheet, you ask for both the data and the shape in one prompt. SheetXAI handles the column arrangement inline.

Try It

Get the 7-day free trial of SheetXAI and open any Google Sheet with recipient data or campaign records, then ask it to do one of the tasks above. The Cardly integration is included in every SheetXAI plan.