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.

Hi,

I have a current connection set up with LeadConnector and Google Drive. The use case is to create a unique Google Drive folder for every new opportunity that is created in LeadConnector. This works functions well, as shown by Steps 1 and 2. 

However, the issue arises when I try to update the existing opportunity in Step 4 (Step 3 is just an email). There is no search function so I tried just matching against First Name + Last Name or email but they just create brand new opportunities instead of updating the exisiting one. Any help would be great!

 

Hi @Chris1234 

Good question.

It would be better to use this Zap action: LeadConnector - API Request

 

HighLevel API: https://highlevel.stoplight.io/docs/integrations/ca75b3ab9e828-update-opportunity

 

If you need help, consider hiring a Certified Zapier Expert: https://zapier.com/experts/automation-ace

@Troy Tessalone Thanks for the reply- Is the above solution the only way to update an opportunity/contact? That seems strange since the actions do say to Update as well. 

@Chris1234 

Sometimes Zap app triggers/actions can be programmed incorrectly on the backend, which might be the case here.

The HighLevel workaround option provides more control albeit a more advanced approach.

@Troy Tessalone Understood and thanks. The issue is that we are currently a subaccount and using your approach requires a level of access which we do not have. 

Terms & Conditions