Description
Hubspot introduced new API for engagements (notes, calls, tasks, meetings, emails). Previous one had a lot of limitations, it could return only 10k recent engagements and because limit was shared some users might experience lack of entities in Fibery (Adam 07-Dec-2022 )
Also, since each engagement type had no separate API endpoint to get it we used to overfetch A LOT (e.g. sync Emails → get all engagements and filter for emails, sync Tasks → get all enagement again and filter for tasks, e.g.)
This should not lead to error in formulas, views or automations if they used one of the changed fields. Instead old field should be ignored by sync-service so it won't appear for new integrations
Migration guide for customers:
Unfortunately, it brings some breaking changes. Few fields changed their inner id and type so we have to re-create them and can't just update the old ones. We tried to make this as less painful as we could so we won't delete your old fields to not break your formulas, views or automations. But they won't be in sync anymore, so we ask you to re-setup them to use new fields
Below you can find affected fields, if you used one of them you might need to fix your formula/view/automation rule:
All engagement databases (Meeting, Note, Email, Task, Call):
Owner and Hubspot Creation Date changed their inner id
Meeting:
startTime renamed to Start Time
endTime → End Time
new field:
Outcome changed type from Text to Single-Select
Email:
new field:
Status changed type from Text to Single-Select
Call:
Status changed type from Text to Single-Select
Disposition changed type from Text to Single-Select
new field:
Direction single-select field with values (INBOUND, OUTBOUND)
Task:
Status changed type from Text to Single-Select
Priority changed type from Text to Single-Select
Type changed type from Text to Single-Select