Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Error while launching Phantom via Zapier – Cannot read properties of undefined (reading 'crmContactField')

  • April 1, 2026
  • 2 replies
  • 10 views
H

Hi everyone 👋,

I’m facing an issue while trying to launch a PhantomBuster Phantom via Zapier and could use some help.

What I’m trying to do

  • Use the “Launch Phantom” action in Zapier
  • Phantom is already set up and works fine when launched directly from PhantomBuster
  • The Zap reaches the Phantom step, but fails during the Test phase

Error message

Failed to create a launch in PhantomBuster
Cannot read properties of undefined (reading 'crmContactField')

Additional details

  • Zapier step: Launch Phantom
  • waitResult = false
  • Phantom ID is being passed correctly (I can see the ID in the test data)
  • No obvious missing required fields in Zapier UI
  • This happens consistently when testing/running the Zap

What I’ve already tried

  • Reconnected the PhantomBuster account in Zapier
  • Re-selected the Phantom instead of using a custom ID
  • Re-tested after saving and refreshing the Zap
  • Verified the Phantom runs normally outside Zapier

Has anyone run into this error before, or know what crmContactField refers to in this context?
Is this related to a specific Phantom type or a required input that Zapier doesn’t surface clearly?

    2 replies

    Troy Tessalone
    Zapier Orchestrator & Solution Partner
    Forum|alt.badge.img+14
    • Troy TessaloneZapier Orchestrator & Solution Partner
    • Zapier Orchestrator & Solution Partner
    • April 1, 2026

    Hi ​@Harshit jain 

    Help link for using PhatomBuster in Zaps: https://support.phantombuster.com/hc/en-us/articles/360007079180-How-PhantomBuster-and-Zapier-Integrate

     

    For us to have more info, post screenshots showing how your Zap steps are outlined and configured.

     

    If you still have issues, try reaching out to PhatomBuster Support for help with their Zap app integration.

    ⚡ Troy Tessalone - AutomationAce.com | Top Zapier Solution Partner | #1 Zapier Community Contributor
    F
    Forum|alt.badge.img+2
    • Fahad SZapier Solution Partner
    • Zapier Solution Partner
    • April 1, 2026

    Hi ​@Harshit jain 

    The error Cannot read properties of undefined (reading 'crmContactField') occurs because PhantomBuster's API expects a crmContactField argument that Zapier isn't passing. You mentioned there are "no obvious missing required fields in Zapier UI"—that's exactly the issue. This field isn't surfaced in Zapier's UI because it's not marked as required in the integration, but your Phantom's configuration still expects it.

    Why it works manually but not via Zapier:

    • When launched from PhantomBuster Dashboard, your saved configuration supplies all arguments

    • When launched via API (what Zapier does), all arguments must be passed explicitly—even ones that don't appear as required fields in Zapier's UI

    The Fix

    Since the field isn't visible in Zapier's UI, you need to add it manually:

    1. Open your "Launch Phantom" action step

    2. Scroll to Input Fields and click "Add Custom Input Field"

    3. Enter:

      • Field Name: crmContactField

      • Value:

        • Not using CRM? Enter "none" or "test"

        • Using CRM? Map it to a contact field from a previous step

    4. Save and re-test

    If that doesn't work, check your Phantom's configuration in PhantomBuster. If you're not actually using CRM, disable the CRM integration there—this will remove the requirement entirely.

    Why this happens
    PhantomBuster's API expects a key-value structure that matches your Phantom's exact argument list. Even if a field isn't marked "required" in Zapier's UI, your Phantom may still expect it based on its saved configuration (especially CRM-related fields). Adding it manually provides the expected structure.

    Supporting Documentation

    Hope this helps!

    If you're still running into issues, drop a screenshot of the error and a quick description of what your Zap is doing, happy to take a look!

    And if you'd rather just get it sorted quickly, I offer a free 20-min Zapier troubleshooting call. Book it under Resources on my Zapier Directory profile: https://zapier.com/partnerdirectory/automatemybiz

     

    Terms & ConditionsAccessibility statement