For teams that run on Flexmail
Flexmail update contact fields from your shop
Segments on last order date or number of orders only work when those fields are filled in. Today that means a fresh CSV import from the shop or CRM, a mapping step each time, and fields that have to exist in Flexmail before the import starts.
How it goes today
- Export customers with their order data from the shop or CRM.
- Save the file as CSV UTF-8 so accents survive the import.
- Map each column to the right Flexmail field and pick a source.
- Read the import summary for skipped and blacklisted rows.
How it can go
Last order date, order count and customer type stay current on your Flexmail contacts.
You forward the customer export on the day you choose. Rows are matched to existing Flexmail contacts by email address and only the fields you picked are updated. People who are not a contact yet are left out, and columns without a matching Flexmail field come back on a short list so you can create the field first.
Say this in ChatGPT, Claude or Copilot
Your chat gets connected to Hypamoon first, with this request filled in. You paste your Flexmail key in the portal, never in the chat.
With Hypamoon, when I forward our customer export, match each row to an existing Flexmail contact by email address and update the fields I name, such as last order date, number of orders and customer type. Leave out people who are not a contact yet, and send me a short list of rows and columns that could not be used.
In Flexmail you create a personal access token under Settings, API, Personal access tokens, and use it with your account ID. It stays yours.
More for teams on Flexmail
- Did this customer not unsubscribe from our newsletter last month?
- Which of our customers actually read the price update?
- She asked us twice to stop the newsletter, why did she get another one?
- How did our mailings do this month compared to last month?
- What do we have on file for this person?
- What do we do with the sign-up sheet from the fair?
- Everything for Flexmail