Mapping form submissions to entities
Studio form definitions store target_entity_type and a JSON field_mapping. The backend currently defaults the target to crm_contact and validates mapped submission fields before processing.
The Forms page’s visual builder edits the form schema, status, slug, and notification email. It does not expose target-entity or field-mapping controls. Existing extra JSON is preserved when a definition is edited, but operators should not infer broader entity support from that behavior.
Use the MCP operations inblack_get_studio_form_definition, inblack_save_studio_form_definition, and inblack_validate_studio_form_submission when an integration needs the full definition contract. The current supported operational target is Customer 360 contact mapping; broader entity targets are not documented as available.