Upload Records with a CSV File | Kizen Basics
Overview
Caution: This setup reflects Kizen's default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
Adding Records one at a time works well for a handful of entries, but it doesn't scale when you need to import many Records at once. A SmartConnector lets you upload a spreadsheet, such as a CSV file, and create or update many Records in a single run instead of repeating the same manual steps.
A Spreadsheet Upload SmartConnector, the most common type, reads the rows in your file, maps each column to a field on the destination Object, and writes a Record for every row.
Let's return to our sample scenario. At one of Flywheel Adventure Park's concession stands, Marcus grabs some nachos, Sofia gets a snow cone, Caleb picks a churro, and Elena orders a lemonade. Rather than creating four separate Concession Records, you'll upload all four purchases in a single run using a CSV file we provide. SmartConnectors are designed for this kind of batch work. You will:
Create a Spreadsheet SmartConnector for the Concessions Object
Map CSV columns to Concessions fields
Validate your upload with a Dry Run before writing any data
Run a Live Run to create the Records
These same steps apply to any Object when you need to add or update many Records at once.
Why This Matters
Efficiency: One upload handles many rows, keeping bulk changes fast as data grows.
Accuracy: A Dry Run checks your file first, catching bad values before anything is written.
Consistency: Every row follows the same mapping, so Records stay consistent at any volume.
Repeatability: Reuse a configured SmartConnector for any future file in the same format.
Before You Begin
To complete this task, you must:
Have permission to create and run SmartConnectors
Have already created the Concessions Object
Have Contact Records for all four Reyes family members, including Elena Reyes
Download the sample CSV file
Download flywheel-concessions-upload.csv below. It contains four new concession purchases for the Reyes family, one per row, with a column for each Concessions field you'll map in the next step.
Caution: This sample file is pre-populated with the Reyes family's concession data for this walkthrough. It's not a blank template, so build a new CSV file when you're ready to upload your own records.
Configure the Connection Trigger
On the canvas, find Connection Trigger and select the pencil icon to edit it.
Confirm the content on the General Settings tab, then select SAVE & CONTINUE to navigate to the Configure Connection tab.
To upload the sample file, select Choose File and upload the flywheel-concessions-upload.csv file.
Select SAVE & CONTINUE to navigate to the Initialize Variables tab.
Match the identifiers
On the canvas, find Upload Concessions, select the three-dot menu, and choose Edit.
On the Unique Identifier(s) Matching tab, align the Kizen fields and the variables, starting with Concession Name → concession_name. You can leave the defaults for the Upload Functions.
Select to ADD FIELD MATCH RULE and align the remaining fields and variables:
Concession Value → concession_value
Primary Contact Record → primary_contact_record
Quantity → quantity
Purchase Date → purchase_date. For this one, change the value for If Multiple Matches Found to Do Not Upload Row.
Select SAVE & CONTINUE.
Configure the Mapping Rules
On the Mapping Rules tab, set the Kizen Field Name for Concession Name to concession_name.
For the view, leave the default: Mapped Fields.
For the unmapped variables, match each Data Source Variable to its Kizen Field. As you do, new rows appear as fields for updating.
Select SAVE.
Configure the Finalize Settings
On the Finalize Settings & Preview tab, leave Variable Name to Assign Output Record (Created or Matched) blank. This upload has only one load step, so there's no later step that needs to reference the matched or created Concessions record.
Leave Variable Type set to UUID (Kizen ID), and leave both of the following blank:
Agentic Workflow(s) to Start on Newly Created Records
Agentic Workflow(s) to Start on Other Matched Records
Leave Agentic Workflow Trigger Suppression set to All Triggers Fire, so the four new Concessions records can trigger any Agentic Workflows configured on the Object, just as Records do when created one at a time.
Select SAVE & CLOSE.
Do a Dry Run
Back on the canvas for the SmartConnector, select the play button to open the Executions page.
Select START DRY RUN and in the new modal, upload the flywheel-concessions-upload.csv file.
Select START. Kizen initiates the run and sends you an email when the run completes. From the email, you can quickly see the starting and end times, as well as a link to a full report.
Confirm all four rows passed with no errors. A Dry Run does not create, update, or modify any Records, so it's safe to run as many times as you need.
Activate and Run a Live Run
Caution: Canceling a Live Run doesn't undo Records it's already written.
Once your Dry Run report looks correct, activate the SmartConnector from the canvas then select SAVE:
Still on the canvas, select the play button to open the Executions page, then choose START RUN. In the modal, upload the flywheel-concessions-upload.csv file again. This time, Kizen writes the four Records to the Concessions Object.
Kizen emails you a report.
What the finished setup looks like
After completing these steps, the Concessions Object shows 5 Records: Popcorn from earlier, plus Nachos, Snow Cone, Churro, and Lemonade from your upload, each with the Primary Contact Record, Quantity, and Purchase Date from your file.
How Bulk Uploads Support Growing Operations
As Flywheel Adventure Park gets busier, more Records need to exist faster than any one person can create them by hand. SmartConnectors keep pace with that growth:
Agentic Workflows: Bulk-created Records can trigger the same automations as manually created ones, so a busy night doesn't mean falling behind on guest follow-up.
Reporting: Dashboards reflect the full day's activity as soon as the Live Run finishes, not just what staff had time to enter by hand.
Data quality: Field mapping applies the same rules to every row, so a rushed evening doesn't introduce inconsistent data.
Other SmartConnector types bring in data automatically, with no file upload. A Scheduler SmartConnector can pull data from an external source, such as a database or S3 bucket, on a recurring schedule. A Webhook SmartConnector collects data that external systems send by webhook and processes it in batches. For more information, see SmartConnectors.
What's Next
Now that you can add Records individually or in bulk, the next step is controlling who can see and edit them. In Configure Your First Permission Groups, you'll create a permission group for Flywheel Adventure Park's staff.
Last updated
Was this helpful?