Your CRM data looks wrong
A record that looks missing in Spiich is usually the first import still running, a change waiting on the five-minute poll, or an object the agent has no access to. Check them in that order.
Spiich keeps one CRM per workspace in two-way sync. When something looks wrong, it is almost always one of four things: the first import has not finished, the change has not arrived yet, the connection needs reauthorizing, or the object or field is switched off for the agent. Work through them in that order.
Is the first import still running?
If Chat shows a "Setting Up Your Workspace" progress screen and will not let you send a message, the first CRM import has not reached 100 percent. Large CRMs take longer. Leave it running: the screen clears itself when the import finishes, and the workspace admin gets a welcome email. The same screen offers an onboarding call while you wait.
Two related symptoms come from the same cause. Settings > Object Types showing "Connect a CRM from Integrations to start syncing object types." means no CRM is connected yet, or no object types have landed. An expanded object showing "No attributes have synced for this object type yet." means that object's fields are still being imported. Wait a few minutes and reload.
A change you made in the CRM has not appeared
Different changes travel by different routes.
| What changed | How it reaches Spiich | Worst case |
|---|---|---|
| An Attio or Pipedrive record, note, task or list | Webhook, pushed as it happens | Seconds |
| A HubSpot contact, company or deal | Webhook, pushed as it happens | Seconds |
| A HubSpot task, note, lead or ticket | The five-minute polling cycle | Five minutes |
| A new, renamed or retyped field, an Attio list or list field, or workspace members | The hourly schema refresh | One hour |
This is also why a list or list field you created in Attio moments ago is not selectable yet when you ask the assistant to add someone to it. Try again after the next hourly refresh.
The "Reconnect to your CRM" banner
A banner above Chat reading "To use the latest spiich features, you need to reauthenticate" means Spiich now needs a permission the existing connection does not hold. It cannot grant that to itself.
If reauthorizing drops you back on Settings > Integrations with "Attio workspace mismatch. Please try again." or "Hubspot workspace mismatch. Please try again.", you signed in to a different CRM workspace than the one Spiich is connected to. Spiich checks the Attio workspace slug, the HubSpot portal ID and the Pipedrive API domain before it accepts new tokens. Sign out of the CRM, sign back in to the workspace or portal that is already connected, then click Reauthenticate again.
The agent cannot see or change a field
Every object and field the agent may read or write is controlled at Settings > Object Types. If Spiich says it cannot find a field, or quietly leaves one alone, check the switches there.
When a Writable switch refuses to turn on, the tooltip names the reason:
- "This object isn't writable" means the parent object row above it is not writable. Turn that on first.
- "Turn on visibility first" means the field's
Visibleswitch is off. - "· Read-only in CRM" means the field can never be written from Spiich. The CRM would reject the write, so it has to be changed in the CRM itself.
An object row carrying a red Sync failed badge is telling you the last attempt to read that object's schema or records failed. Hover the badge: it shows the reason the CRM returned. Most are a missing CRM permission, which an admin fixes by reauthorizing, or an object that does not exist on your CRM plan. More detail in Control what Spiich can read and write.
A save came back as a CRM error
A message starting "Hubspot error:", "Attio error:" or "Pipedrive error:" means the CRM rejected the write, usually because a required field is missing or a value is invalid. Spiich rolls its own change back so the two systems never disagree, which is why the record appears to vanish again. Read what the CRM asked for, fill it in, and save again. Creating a HubSpot ticket always needs a ticket status, and Spiich refuses that write up front rather than letting HubSpot reject it.
If the assistant says an object "is not enabled for this customer" when asked to create a lead or a ticket, that HubSpot object has not been connected for the workspace or has been switched off. An admin turns it on at Settings > Object Types. Non-admins get "Connecting a HubSpot object requires an admin."
Records that were never imported at all
- Attio custom objects arrive switched off. Turn the ones you want on individually under
Settings > Object Types > Custom objects. - Attio's own Users and Workspaces objects are never imported.
- HubSpot Leads and Tickets only exist where the portal has those products. Where an object is missing, Spiich skips it rather than failing the whole sync.
- Emails synced in from Attio are visible only to the people who were on the message.
Still stuck
Email hello@spiich.ai with the record or field, the CRM it lives in, and the exact error text. Switching a workspace from one CRM to another is also a support request, not something you can do yourself, so start there too. You can reach us through the contact form.