Giving an AI employee your own list of stores, customers or sites
Your stores, customers and target accounts make an AI employee far more useful. How to prepare the list, bring it in, and what the employee can do with it.
To give an AI employee your own list, upload it as a CSV or link a sheet from Google Sheets in the My data block, with one row per place and a name and an address or a position in each row. The employee can then work around each of your places (what opened near each store), skip what is already yours (existing customers left out of a lead list), or check each row on a schedule (has a target account closed or moved). A clean list with positions is the difference between generic results and results about your business.
This is for teams with a spreadsheet of stores, branches, customers, depots or target accounts. It covers what a usable list looks like, the four ways an employee uses one, a made-up example, the mistakes that make lists fail quietly, and the blocks to use.
What a usable list looks like
- One row per place, with a header row naming the columns.
- A name in a column called name, or one called store, site, branch, company or account.
- A position: latitude and longitude columns are best. Without them, a full street address with the city gives each row a position; a city alone places it at the city's centre.
- Your own columns: region, manager, tier, account number. They travel with each item and can appear in the email.
- Within the limits: up to 5,000 rows and 40 columns in a table.
Four ways an employee uses your list
| What you want | Block | What it does |
|---|---|---|
| Work around each of my places | My data as the start | Each row becomes an item with a position; the next blocks search around it |
| Leave out what is already mine | Match with my table | Keeps only found places that are not in your table, or only those that are |
| Tag each result with my nearest site | Find nearest | Adds the nearest of your points and the distance to each result |
| Start when someone adds a row | New rows | Runs the flow on each row added to the table or sheet |
The same table can feed several AI employees at once; update it once and they all follow.
For a one-off job rather than a standing employee, My data's Enrich a list adds positions, rating, phone, website and category to up to 100 rows at a time, with the price shown first.
A worked example
A made-up case: a chain of 18 bike shops in Amsterdam keeps its shops in a spreadsheet with an address and a manager's email for each. It wants every manager to hear when a new bike shop or repair stand opens near them.
- The spreadsheet is uploaded in the My data block. The rows have no coordinates, so each gets a position from its address. Two rows with only a district name are placed at the district's centre; the operations lead fixes their addresses and uploads again.
- Nearby places, set to Each incoming place, looks for bike shops and repair shops within 1 km of each store.
- Only new keeps only places not seen before.
- Match with my table drops the chain's own shops, which sit within 1 km of each other in the centre and would otherwise come back as competitors.
- Email, set to one email per item, writes to the manager email column of the store each new shop is near.
In this invented first week, three managers each get one email naming a new shop near them; the other fifteen get nothing, which is correct. Without the step that drops the chain's own shops, every manager would have been told about their colleagues' shops.
Mistakes that make lists fail quietly
- No positions. Rows without coordinates or a usable address still come in, but blocks that search around a place have nothing to search around.
- Vague addresses. A row that says only "City centre" lands at the city's middle. Check the map after the first upload.
- Duplicates. The same store twice means two alerts. Clean the sheet, or put Remove duplicates after My data.
- An old copy. A list uploaded once goes stale. Link a sheet from Google Sheets, or upload again when stores open or close.
- Personal details you do not need. Bring in only the columns the employee uses; leave out personal phone numbers and notes.
How to set it up
- Open the My data block's settings and upload the CSV or paste the sheet's link. The table is also listed on the My data page.
- Check the map of the rows for anything out of place.
- Choose the job: start from the list (My data first), compare against it (Match with my table), or tag results with your nearest site (Find nearest).
- Add the data and AI blocks the job needs, then Email, Google Sheets or Slack.
- Run a test and open a few items to see your own columns on them.
What lands in the inbox reads like your own list: each result with your store's name, region or manager beside it. Templates built on your own list include What opens near my stores, Watch my target accounts and Check new merchants from my sheet.
Questions
What format should my list be in?
A CSV file or a sheet in Google Sheets, with a header row, one place per row, a name and either latitude and longitude or a full address.
How big can the list be?
Up to 5,000 rows and 40 columns in a table. Find nearest takes up to 2,000 points.
What if my list has no coordinates?
Rows get a position from their address and city columns. Check the result on the map, and add fuller addresses where a row landed in the wrong place.
Will the employee see changes I make to the sheet?
A linked sheet is read again when you bring it in again; the New rows trigger runs a flow as soon as rows are added. A one-off upload stays as it was until you upload again.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates