Skip to main content
Question

Manatal ATS Custom Field Mapping

  • November 20, 2025
  • 3 replies
  • 24 views

Hi Zapier Community! 👋

I'm trying to set up a Zap that syncs new candidates from Manatal ATS to Airtable, but I'm running into issues with mapping custom fields. Hoping someone here has cracked this code!

My Setup:

  • Trigger: Manatal - New Candidate
  • Action: Airtable - Create or Update Record
  • Goal: Map individual custom fields from Manatal to specific Airtable columns

The Problem:

In the field mapping, I can see a generic "Custom Field" option, but I need to access individual custom fields by name (e.g., "Salary Expectation", "Years of Experience", "Preferred Location", etc.).

When I test the Manatal trigger, the custom_fields output shows as an empty array [], even though I know candidates in Manatal have custom fields populated.

What I've Tried:

✅ Tested the trigger with real candidate data
✅ Verified custom fields exist and are populated in Manatal
✅ Checked field mapping options - only see generic "Custom Field"
✅ Confirmed I have proper permissions in Manatal

Questions:

  1. Has anyone successfully mapped individual Manatal custom fields? If so, how?
  2. Does Manatal's API expose custom fields differently? (nested structure, separate endpoints, etc.)
  3. Are there any workarounds? (Formatter steps, webhooks, etc.)

Technical Details:

  • Manatal API version: 3.0.3
  • Airtable API version: 3.10.0
  • Custom fields in test data show as: "custom_fields": []

Any insights would be hugely appreciated! I'm happy to share more details about my setup if it helps troubleshoot.

Thanks in advance! 🙏

Sean

3 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • November 20, 2025

Hi ​@sagatep 

For us to have more info, post screenshots showing the DATA OUT for the custom fields from Manatal so we can see how the data is structured.


robintrainward
Zapier Orchestrator
Forum|alt.badge.img
  • Zapier Orchestrator
  • November 20, 2025

Hi ​@sagatep,

 

You can try including an additional step after the trigger that calls https://api.manatal.com/v3/candidates/{{candidate.id}}?include=custom_fields 

 

You can populate candidate ID from the trigger event

 

Hope this helps!

 

-Robin


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • November 20, 2025

@sagatep 

If custom fields are not returned from the Zap trigger step, then try adding this Zap action step: Get Candidate

See if that returns the Candidate custom fields.