When Tapistro sends data to HubSpot, the value must match what that property type expects. If it doesn't, HubSpot will reject the update. The sections below cover the format requirements for each type.
Property Type Compatibility
Dropdown select and Radio select
Only values that already exist in the property's options list are accepted. HubSpot will not create new options automatically. Confirm all possible Tapistro output values have a matching entry before activating.
Checkbox (single)
Send Yes or No as a string. Do not send true, false, 1, or 0.
Number
Plain numeric value only. No commas, currency symbols, or units. Send 15000, not $15,000.
Date
YYYY-MM-DD format at midnight UTC. Example: 2024-09-15.
DateTime
Unix timestamp in milliseconds. Example: 1726358400000.
Single-line text and Multi-line text
Any string. HubSpot caps string properties at 65,536 characters. Keep this in mind if Tapistro is generating longer AI-written content for this field.
Phone and Email
Both are stored as strings. HubSpot expects a valid email format ([email protected]). Phone has no enforced format at the API level.
Custom vs. Standard Properties
Standard properties have fixed types. Custom properties are configured by your HubSpot admin. If Tapistro is syncing to a custom dropdown or radio select, the property and all its options must exist in HubSpot before the sync runs. Tapistro cannot create HubSpot properties.
Validate Before You Activate
For any Destination writing to a dropdown, radio select, or checkbox property:
Go to HubSpot > Settings > Properties and open the target property.
Confirm every value Tapistro could output has an exact match in the options list.
If a value is missing, add it before activating the Journey.
Tips
Option matching can be case-sensitive. If a dropdown update is failing, check the casing against what's defined in HubSpot.
Test on a small batch of records before running the Journey across your full list.