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.

Based on the creation of a ZenDesk task assigned to a view (the triggering action for the Zap), I am wondering if it’s possible for Zapier to determine which object a record is in based on a single field manually inputted on the ZenDesk ticket.

For example, the ZenDesk ticket has an ID. That ID is unique to the customer and would be unique in Salesforce, and it could be across either the Lead or Account objects. Can you use Zapier to query a Find Records in a single action that remembers if the record is a Lead or an Account record?

I understand this goes against how SOQL works. What I’m trying to achieve is to have the zap follow different pathways based on the object type. For Lead, one pathway. For Account, a separate pathway. I don’t think setting up two Find Records, one running after another, would solve what I’m trying to achieve.

Hi ​@ZapFan567 

Feedback to consider…

 

Key Points to Understand

  1. Salesforce Object Model
    A Salesforce record belongs to exactly one object (Lead, Account, Contact, etc.). SOQL queries must target one object at a time—you can’t query multiple objects in a single Find Record action in Zapier.

  2. Zapier’s “Find Record” Limitation
    Zapier’s built-in Salesforce “Find Record(s)” action requires you to choose the object type up front.
    That means:

    • You can run “Find Lead” or “Find Account,” but not “Find either one” in a single step.

    • Zapier doesn’t “remember” the object type automatically from a single search.

Possible Approaches

1. Sequential Search + Conditional Path

  • Step 1: Try a “Find Lead” action using the Zendesk ID.

  • Step 2: If no Lead is found, run a “Find Account” action.

  • Step 3: Use Paths or Filters to branch based on which step returned a result.
    Pro: No need for external tools.
    Con: You’ll have two search calls, which might matter for task usage.

2. Use Salesforce Apex REST Endpoint (Advanced)

  • Create a custom Apex REST service in Salesforce that:

    • Accepts the ID.

    • Checks both Lead and Account objects in one SOQL call (or sequentially in Apex).

    • Returns the object type and record data.

  • Call that endpoint from Zapier with “Webhooks by Zapier.”
    Pro: Single call returns exactly what you need.
    Con: Requires Salesforce development.

3. Use an External Helper (e.g., Airtable or Google Sheets)

  • Sync Salesforce IDs + object type to an external table.

  • In Zapier:

    • Search that helper table to find object type.

    • Then route the Zap accordingly.
      Pro: No Salesforce dev needed.
      Con: Requires maintaining the sync.

Direct Answer to the Core Question

“Can Zapier query both objects in one step and remember the type?”
No—not with the standard Salesforce Zapier actions. You’ll either need to:

  • Run two searches and branch based on results (most common), or

  • Build a custom Salesforce API endpoint or middleware to do the combined search.

 

Hi ​@ZapFan567 👋 Did Troy’s reply help to point you in the right direction?

Want to make sure you’re all set here, so please keep us posted on how things are progressing!

Terms & ConditionsAccessibility statement