HubSpot: Map HubSpot Values to respond.io Values
Z
Zy
Business Problem:
Mapping a HubSpot property to a respond.io field may not be enough when the two systems use different options. A HubSpot value such as “Qualified” may need to map to a respond.io value such as “Sales-ready.”
Desired Outcome:
- Map Individual Options: Let admins pair HubSpot dropdown values with the corresponding respond.io field values.
- Identify Unmapped Options: Warn admins when a HubSpot value has no matching respond.io option, so they can fix the mapping before data is lost or misrepresented.
Use Cases:
- Different Labels for the Same Status: Map HubSpot’s “MQL” option to the corresponding respond.io “Marketing qualified” option.
Current Workaround:
Teams may need to keep option names identical in both systems.