Syncing Airtable checkbox with GoHighLevel using Make: Need advice

Other Questions Airtable
1

I’m struggling to get a checkbox from Airtable to sync with GoHighLevel using Make’s LeadConnector module. It’s driving me crazy!

Here’s my setup:

Airtable:

  • Checkbox field called ‘Veteran’ (true/false)

GoHighLevel:

  • Custom field ‘Veteran’
  • Checkbox/multi-select option ‘Veteran?’

I’ve tried matching Watch Records to the custom field, but no luck. I’ve also played around with set variables and different mapping expressions.

Nothing seems to work. Any tips or tricks? Has anyone done something similar before? I’d really appreciate some help figuring this out. Thanks!

2

I’ve encountered a similar issue when syncing checkboxes between Airtable and GoHighLevel. The key is to use a formula in Make to convert the Airtable boolean to a format GoHighLevel expects. Try this approach:

  1. In your Make scenario, after the Airtable module, add a ‘Set variable’ step.
  2. Create a formula: if({{1.Veteran}}, “Veteran?”, “”)
  3. In the GoHighLevel action, map this new variable to the ‘Veteran’ custom field.

This should translate the true/false from Airtable into either “Veteran?” or an empty string for GoHighLevel. Make sure your GoHighLevel field is set up to accept text input rather than a strict boolean. Let me know if you need any clarification on these steps.

3

hey there! i’ve dealt with this before. the trick is to use a text formula in Make to change the airtable boolean. try this:

if({{1.Veteran}}, “Veteran?”, “”)

map that to ur GHL field. make sure the GHL field is set for text input, not strict boolean. hope this helps!

4

I’ve been down this road before, and it can be frustrating. Here’s what worked for me:

Instead of trying to sync the boolean directly, use a Text formula in Make to convert it. Something like this should do the trick:

if({{1.Veteran}}, “Yes”, “No”)

Then, in GoHighLevel, set up your custom field as a dropdown with “Yes” and “No” options instead of a checkbox. Map the formula result to this field.

This approach gives you more flexibility and avoids the boolean translation issues. It also makes it easier to filter or sort in GoHighLevel if needed.

Just remember to update any existing automation or reporting that might be relying on the checkbox format. It took me a bit of tweaking, but it’s been smooth sailing since I made this change. Good luck!