Map your CRM fields
Settings > Field Mapping points Spiich's fixed set of People, Organization, Deal and Task fields at your CRM's own attribute names, so data reads from and writes to the right place.
Before you start
- A CRM is connected to your workspace.
Spiich has its own fixed idea of a person, an organization, a deal and a task. Your CRM has its own field names for the same things, and they rarely match exactly. Settings > Field Mapping is where you tell Spiich which of your CRM's attributes holds which of its fields, so a contact_email or primary_email_address column in your CRM lines up with the field Spiich calls email.
What field mapping does
Object Types decides whether the agent can see and write a whole object or field. Field Mapping is narrower and more precise: it tells Spiich which specific CRM attribute answers a specific standard question, such as which of your CRM's fields holds a person's email address, or which one is the deal's close date. Get the mapping right and the assistant, Tables and every prompt column read from the correct source. Leave a field unmapped and Spiich simply does not have an attribute to read for it.
Field Mapping covers four object types: People, Organizations, Deals and Tasks. HubSpot Leads and Tickets are not part of it.
Map a field
Open Field Mapping
Go to
Settings > Field Mapping. If the page is missing, connect a CRM first at Connect your CRM; the entry only appears once one is connected.Pick the object tab
Choose People, Organizations, Deals or Tasks. Each tab shows a progress bar and an x-of-y mapped counter for that object.
Choose the CRM attribute
Each row lists one Spiich field on the left. Use the CRM attribute dropdown on the right to pick the matching attribute from your CRM. A row you have not touched yet reads
Not mapped.Confirm the save
Spiich confirms with Saved, Field mapping updated., and the row's dot turns green. There is no separate save button; each row saves on its own.
Undo a mapping if you need to
Click the X at the end of a mapped row to clear it. Spiich confirms with Removed, Field mapping removed., and the row goes back to
Not mapped.
The fixed field list
Spiich does not let you invent new fields here. Each object has a fixed set of Spiich fields, and you are only choosing which CRM attribute answers each one.
| Object | Spiich fields |
|---|---|
| People | name, first_name, last_name, email, phone, role, linkedin, location, organization, owner, last_activity_date, created_date, added_by_spiich |
| Organizations | name, location, website, linkedin, owner, icp_fit_score, industry, last_activity_date, created_date, added_by_spiich |
| Deals | name, owner, pipeline, stage, value, status, expected_close_date, contact, organization, last_activity_date, created_date, added_by_spiich |
| Tasks | text, updated_at, assignee, due_date, done, type, added_by_spiich |
If a tab shows No canonical fields are defined for this entity type yet, Spiich has not defined a fixed field list for that object, and there is nothing to map on that tab yet.
One attribute, one field
Each CRM attribute can only answer one Spiich field at a time. Once you map contact_email to People's email, that same attribute is filtered out of every other dropdown on that tab, so you cannot accidentally point two Spiich fields at the same source. Remove the mapping first if you want to reassign the attribute somewhere else.
You can ask the assistant about the current state instead of opening the page yourself.
Are my deal fields mapped?
The assistant reports which CRM is connected and how many field mappings exist for an object, and links you to the right Settings page instead of guessing.
Limits
- Field Mapping only covers People, Organizations, Deals and Tasks. HubSpot Leads and Tickets are deliberately left out.
- The Spiich field list per object is fixed. You choose the CRM attribute; you cannot add a new Spiich field here.
- One CRM attribute maps to exactly one Spiich field. Mapping it elsewhere means removing the existing mapping first.
- A field left unmapped is not an error. It just means that field has no source to read from until you map it.
- The page and its Settings entry only exist once a CRM is connected. Nothing is defined ahead of that.
If something goes wrong
Settings > Field Mapping does not appear in the navigation. No CRM is connected yet. Connect one at Connect your CRM and the entry appears.
*A tab says No canonical fields are defined for this entity type yet.*** There is nothing to map on that object; check a different tab.
*The page shows Failed to load field mappings. Please refresh and try again.*** A one-off loading error. Refresh the page.
A CRM attribute you expect is missing from the dropdown. It may already be mapped to a different Spiich field on the same tab. Check the other rows, or remove the existing mapping and reassign it.