What is Custom Field Mapping?
Custom Field Mapping uses AI to analyze your deal context — transcripts, documents, and notes — and extract structured insights based on the MEDDPICC sales qualification framework. These insights are written directly to custom fields on your Salesforce Opportunities or HubSpot Deals, so your CRM stays current without manual data entry.
Two Types of Fields
Fluint supports two types of insight fields:
Fluint-defined fields — 9 pre-set fields based on the MEDDPICC framework. These come built-in and cannot be removed, but you can disable any field by selecting "Not Mapped" from its CRM field dropdown.
User-defined fields — Custom fields you create yourself. You write the extraction prompt, choose the value type, and map them to your CRM just like the built-in fields.
Both types work the same way: Fluint extracts values from your deal context and syncs them to the CRM fields you've mapped.
Fluint-Defined Fields
Fluint comes with 9 pre-set fields out of the box:
Field | Type | How It Works |
Has Business Case | Boolean | Automatically detected when a business case document exists in the deal |
Metrics | Text | Quantified business outcomes the buyer expects (revenue increase, cost reduction, time savings) |
Economic Buyer | Text | The individual with discretionary spending authority — name, title, and relationship to the deal |
Decision Criteria | Text | Evaluation criteria the buyer will use to select a solution |
Decision Process | Text | Key stages, stakeholders, approval requirements, and expected timeline |
Paper Process | Text | Procurement steps, legal review, security/compliance reviews, and contract execution dependencies |
Identified Pain | Text | Primary business pains driving the initiative and their organizational impact |
Champion | Text | Internal advocate — name, title, personal motivation, and level of influence |
Competition | Text | Alternatives the buyer is considering: competing vendors, internal build options, and the status quo |
Text fields contain up to 500 characters of AI-extracted insight. Fields return empty if there isn't enough deal context to make a confident extraction.
You don't have to use all 9 fields. To skip a field, select "Not Mapped" from its CRM field dropdown — it won't be synced to your CRM.
How to Set Up in Your CRM
Before linking fields in Fluint, you need to create the corresponding custom fields in your CRM.
Salesforce
Navigate to Setup > Object Manager > Opportunity > Fields & Relationships
Click New to create a custom field for each Fluint field you want to sync
For text fields (Metrics, Economic Buyer, etc.): Choose Long Text Area — this supports up to 131,072 characters. Standard Text fields max at 255 characters and may truncate your insights.
For Has Business Case: Choose Checkbox
Save each field
HubSpot
Navigate to Settings > Properties > Deal Properties
Click Create property for each Fluint field you want to sync
For text fields: Choose Multi-line text or Single-line text
For Has Business Case: Choose Single checkbox
Save each property
Linking Fields in Fluint
Once your CRM fields are created:
Go to Settings > Integrations > [Your CRM] > Manage
Enable the Custom Field Mapping toggle
For each Fluint field (both Fluint-defined and user-defined), select the matching CRM field from the dropdown
Click "Save Changes" to save your mappings
Important: Your field mappings are not applied until you click Save Changes. If you navigate away without saving, your changes will be lost.
Fluint automatically discovers the custom fields available on your CRM object, so they'll appear in the dropdown as soon as they're created in your CRM.
User-Defined Fields
Beyond the 9 Fluint-defined fields, you can create your own custom fields to extract any insight you need:
Click Add Custom Field
Enter a label (e.g., "Security Review Status")
Write a description/prompt that tells the AI what to extract (e.g., "Summarize the current status of any security or compliance reviews mentioned in deal conversations")
Select a value type — String (text) or Boolean (yes/no)
Click Save to create the field
Map it to a CRM field using the same dropdown workflow as the Fluint-defined fields
You can create up to 50 user-defined fields per organization.
When to Expect Synced Data
Initial extraction is triggered when a transcript is processed or a document is created/updated in a deal
AI extraction uses batch processing — expect results within up to 24 hours
Subsequent updates happen automatically as new deal context is added (meetings, documents, notes)
CRM sync occurs automatically after extraction completes
The "Has Business Case" field updates immediately since it doesn't require AI extraction — it checks whether a business case document exists in the deal.
Known Limitations
Field value types: Only string (max 500 characters) and boolean are currently supported
Salesforce field type: Use "Long Text Area" fields to avoid truncation — standard Text fields cap at 255 characters
Null values: AI extraction may return empty if there isn't enough evidence in the deal context
One catalog per deal: Field values reflect the entire deal context, not individual meetings
Custom field limit: Maximum 50 custom fields per organization
Extraction timing: Batch processing can take up to 24 hours; results are not instant
Troubleshooting
Fields not appearing in the CRM dropdown
Verify the custom field exists on the correct CRM object — Opportunity in Salesforce, Deal in HubSpot
Check that the field was created as the right type (Long Text Area for text, Checkbox for boolean)
Try refreshing the page — Fluint fetches available fields when the mapping UI loads
Values not syncing to CRM
Confirm the Custom Field Mapping toggle is enabled
Check that field mappings are saved — you must click Save Changes after updating any mappings
Ensure your CRM integration is connected and active in Settings > Integrations
Fields showing empty/null values
This is expected when there isn't enough deal context for a confident extraction
Add more meetings, documents, or notes to the deal to give the AI more context to work with
The "Has Business Case" field requires a business case document to exist in the deal