💡 How to: Prepare Bulk Imports for Zenput
| The bulk importer is an internal tool that Zenput uses to help manage customer hierarchies and operational schedules. Using CSV templates with a consistent structure ensures data is not overwritten and duplicate entries are not created. This guide covers how to prepare imports for locations, users, and calendar events. |
🔍 Navigate this article: |
When to use bulk imports for hierarchy
There are several reasons why you may want to utilize the bulk importer for your location hierarchy and users:
- Adding a list of 10+ locations
- Changing information for existing locations in bulk (email, phone number, name of the location, or General Attributes associated with a location)
- Adding or updating users to multiple locations at once
- Moving locations and/or users from different teams
- Removing a list of locations from your account at once
- Adding Regions to existing locations to enable the use of Location Attributes
Tip: To gather information for your existing locations to provide to support, see this article: How to: Export Locations
Location and user information are separated into different templates. Below you will find the templates and information on the necessary column titles required for uploading information.
Location Template
Use this template when adding new locations or updating existing location information.
Example Template: View Location Template Example
| Column Name | Required? | Description |
|---|---|---|
|
Name (Column A) |
● Required |
The exact name the location will be called in Zenput.
|
|
Address (Column B) |
● Required |
The street address of the location in Zenput.
|
|
City (Column C) |
● Required | The city the location is in. |
|
State (Column D) |
● Required |
The state the location is in.
|
|
Country (Column E) |
● Required |
2-digit ISO country code.
|
|
Zip (Column F) |
● Required | Zip or postal code of location. |
|
Region (Column G) |
● Recommended | To allow the use of Location Attributes, this column must be included. |
|
Email (Column H) |
Optional |
The email address of the location (can be more than one).
|
|
Phone (Column I) |
Optional |
Phone number of location.
|
|
External Key (Column J) |
● Required IMPORTANT |
Every location must have a unique external key. This can be any combination of numbers and/or letters you prefer, but each individual location MUST have a unique key in the company.
|
|
Active (Column K) |
Optional |
Use this column if you want to deactivate a current list of your locations.
|
|
Lat (Column L) |
Optional |
Latitude coordinates for the location.
|
|
Long (Column M) |
Optional |
Longitude coordinates for the location.
|
|
Team0 (Column N) |
Optional |
A four-digit Team ID that the system creates.
|
|
Team Action (Column O) |
Optional |
Options: blank = no change, 0 = deactivate, 1 = activate
|
|
General Attributes/Tag(s) (Columns P, Q+) |
Optional |
You can have as many or as few general attributes as you want.
|
|
Tag Action (Column R) |
Required (when tags present) |
The action to perform on the General Attributes:
|
User Template
Use this template when adding new users or updating existing user assignments.
Example Template: View User Template Example
| Column Name | Required? | Description |
|---|---|---|
|
First Name (Column A) |
● Required |
The exact first name the user should be assigned.
|
|
Last Name (Column B) |
● Required |
The exact last name the user should be assigned.
|
|
Email (Column C) |
● Required |
Unique email for each user account is required.
|
|
Role (Column D) |
● Required |
The role the user should be assigned (must be an existing role in your company).
|
|
Permission (Column E) |
● Required |
The permission level that should be assigned to the user.
|
|
Team Name (Column F) |
● Required | The exact name of the team, as it appears in the UI (User Interface), where the user is being added. |
|
External Key (Column G) |
Optional | Only necessary if adding users to existing locations. |
Next Steps
After preparing your CSV files using the templates above:
- Review your files to ensure all required columns are complete and accurate
- Verify that External Keys are unique (for location imports)
- Contact Zenput Support team to process the import
Calendar Events Bulk Import
Calendar Event attributes can be used to manage your locations' operational schedules using business events occurring at specific times, such as store opening/closing hours, delivery days, employee shift start/end times, and more. These attributes can also be used to have projects automatically repeat tasks based on store hours, such as performing specific actions every hour while the store is open.
Setting Up Calendar Events
For those new to Calendar Events, your CSM will need to import 7 CSV files, one for each day of the week. To prepare those files based on the schedules you want to set, copy and edit the spreadsheet below:
Copy this spreadsheet to Google Sheets: Calendar Events Import Sheet
Preparing the Import
Once you have copied the sheet, follow the steps outlined in this quick guide to prepare your import:
Show me how: To Schedule Projects Using Calendar Events
Note: You can return to the training guide at any time or share it with others on your team. Once your calendar events are configured, projects can automatically trigger based on your operational schedules.
Next Steps
After preparing your CSV files using the templates above:
- Review your files to ensure all required columns are complete and accurate
- Contact your Customer Success Manager to process the import
- Your CSM will validate the data and complete the import for you
Need Help? If you have questions about preparing your bulk import files, reach out to your Customer Success Manager.
Comments
0 comments
Please sign in to leave a comment.