Title: Force field as boolean
Last modified: October 8, 2025

---

# Force field as boolean

 *  Resolved [giangel84](https://wordpress.org/support/users/giangel84/)
 * (@giangel84)
 * [6 months, 3 weeks ago](https://wordpress.org/support/topic/force-field-as-boolean/)
 * Hello,
   is there a way to force a mapped field to be treated as boolean?Example:
   I have a field “checkbox” on my form, when I map that field on the custom API
   it send all fields as string.Sometimes the endpoint expect some fields are exactly{:
   true } instead of { : “true” }.Any suggestion would be very appreciated.Thank
   you in advance.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [abrarfaisal87](https://wordpress.org/support/users/abrarfaisal87/)
 * (@abrarfaisal87)
 * [6 months, 3 weeks ago](https://wordpress.org/support/topic/force-field-as-boolean/#post-18672910)
 * Hi [@giangel84](https://wordpress.org/support/users/giangel84/) ,
   Thank you for
   sharing the details of your question.
 * Currently, Bit Integrations does not have a built-in option to convert string
   values to boolean directly. However, you can achieve the desired result by creating**
   two separate integrations** and using **custom values** along with **conditional
   logic**.
 * Here’s how you can do it:
    1. **First Integration:**
    2.  - Map your checkbox field and set a custom value of **1** to represent `true`.
        - Add a conditional logic rule: _Run this integration only if the checkbox 
          is selected (true)._
    3. **Second Integration:**
    4.  - Map the same checkbox field but set a custom value of **0** to represent `
          false`.
        - Add a conditional logic rule: _Run this integration only if the checkbox 
          is not selected (false)._
 * For example, if a user submits the form with the checkbox selected, they can 
   be added to **List A**. If the checkbox is not selected, they can be added to**
   List B**.
 * Let me know if this solution works for your setup.
 *  Thread Starter [giangel84](https://wordpress.org/support/users/giangel84/)
 * (@giangel84)
 * [6 months, 3 weeks ago](https://wordpress.org/support/topic/force-field-as-boolean/#post-18673605)
 * [@abrarfaisal87](https://wordpress.org/support/users/abrarfaisal87/) Thank you,
   this could be a solution but it’s applicable only when you have a single field
   to treat as boolean…otherwise you need to build a lot of conditions.
   I hope you
   could take this case as a feature request, in order to improve your plugin in
   the next future.Thank you.
 *  Plugin Support [abrarfaisal87](https://wordpress.org/support/users/abrarfaisal87/)
 * (@abrarfaisal87)
 * [6 months, 2 weeks ago](https://wordpress.org/support/topic/force-field-as-boolean/#post-18677570)
 * Hi [@giangel84](https://wordpress.org/support/users/giangel84/),
   Thank you for
   your suggestion, we have added this as a feature request, if we get more user
   requests for this, we will definitely add it. We have a different product where
   we have the functionality to change the String values to boolean values.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Force field as boolean’ is closed to new replies.

 * ![](https://ps.w.org/bit-integrations/assets/icon-256x256.gif?rev=3291200)
 * [Bit integrations - Easy Automator with no-code automation, integrate Webhook and automate 300+ Platform](https://wordpress.org/plugins/bit-integrations/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/bit-integrations/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/bit-integrations/)
 * [Active Topics](https://wordpress.org/support/plugin/bit-integrations/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bit-integrations/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bit-integrations/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [abrarfaisal87](https://wordpress.org/support/users/abrarfaisal87/)
 * Last activity: [6 months, 2 weeks ago](https://wordpress.org/support/topic/force-field-as-boolean/#post-18677570)
 * Status: resolved