1. IP-based meeting routing
HubSpot captures IP city and IP state, but these fields are not usable in form logic or workflows for real-time or conditional meeting scheduling. This limits our ability to route meetings dynamically based on visitor location, which is critical for region-based sales ownership in B2B teams.
We’d like support for using IP-based fields in:
- Form logic
- Workflow enrollment and branching
- Conditional meeting routing in real time
2. Advanced logic support in legacy forms
Legacy forms currently support only basic if–else logic, while step forms allow more advanced conditional logic. Specifically, legacy forms do not support:
- Actions triggered by multiple combined conditions (e.g., condition A + B + C)
- Applying multiple conditions on the same field
These capabilities are available in step forms but not in legacy forms, creating a gap for teams that rely on legacy forms for existing website flows and integrations.
Enhancing legacy form logic would significantly improve routing, personalization, and operational flexibility for complex B2B use cases.