Data Type Formatting for Custom Fields
In Exabloom, many workflow triggers and actions allow you to map values to custom fields. To ensure data accuracy and smooth processing, it's essential that mapped values follow the correct format based on the data type of the custom field.
This guide provides a clear reference for properly formatting data when mapping values to custom fields.
📌 Supported Data Types & Formatting Requirements
| Data Type | Expected Format | Example |
|---|---|---|
| Text / Multiline Text | Any value (free text) | "Customer is interested in Product X." |
| Time | hh:mm A (12-hour format with AM/PM) | "03:20 PM", "11:15 AM" |
| Date | DD/MM/YYYY (Day/Month/Year) | "20/03/2025" |
| Date Time | DD/MM/YYYY hh:mm A | "27/02/2025 03:45 AM" |
| Single Select / Multi Select | Must match an existing option (case-sensitive) | "Facebook Ads" (if this is an option) |
| Number | Only numerical values (supports both integers & decimals) | 1500, 99.99 |
💡 Ensuring correct formatting helps avoid data entry issues and improves workflow automation accuracy.
🛠️ How to Map Custom Fields in Workflows
Whenever you configure an action in a workflow (e.g., Create Lead, Update Contact, Create Task, etc.), you will see an option to map values to custom fields.
Here’s how to do it correctly:
1️⃣ Identify the Target Custom Field
Each custom field has a specific data type (Text, Date, Number, etc.), which determines how the value should be formatted.
2️⃣ Use Dynamic Values or Fixed Inputs
You can either:
- Enter a fixed value manually (e.g., setting
"Facebook Ads"for the "Source" field). - Select a dynamic value from the workflow (e.g., mapping
{{lead.source}}to a custom field).
3️⃣ Ensure Proper Formatting
- If mapping a Date field, ensure the value follows
DD/MM/YYYY. - If mapping a Time field, ensure it follows
hh:mm A. - If mapping a Single Select or Multi Select field, ensure the value matches one of the predefined options.
4️⃣ Test Before Finalizing
To avoid issues, send a test request through the workflow to verify that mapped values are appearing correctly in the system.
📢 Common Mistakes & How to Fix Them
| Issue | Cause | Solution |
|---|---|---|
| Date is not saving correctly | Using incorrect format (e.g., March 20, 2025) | Use DD/MM/YYYY (e.g., "20/03/2025") |
| Time is not saving | Missing AM/PM or using 24-hour format | Use hh:mm A (e.g., "03:45 PM", not "15:45") |
| Single Select / Multi Select value is rejected | Value does not match an existing option | Ensure the input is exactly the same as one of the options (case-sensitive) |
| Number field not accepting input | Entering non-numeric characters | Ensure the value is only numbers (e.g., 1500, not "1,500" or "1.5k") |
📌 Why Proper Formatting Matters
✔ Prevents workflow errors and ensures smooth automation.
✔ Ensures data integrity, making reports and analytics accurate.
✔ Improves efficiency by reducing manual corrections.
By following this guide, you’ll ensure that every action in your workflow correctly maps and processes custom field values, keeping your data structured and reliable. 🚀