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.

I have been connecting Zendesk to a salesforce account. I try to create cases and import comments from salesforce to zendesk.

I also have a use case that is bringing some problems. This is the use case:

  • When I add an attachment of a case to Salesforce → please find an existing ticket on zendesk → if the custom field with the Salesforce ID is the same as the Case of the attachment → please add an attachment to Zendesk

On a specific day, I can go to salesforce and see an attachment was made but I didn’t receive the attachment nor in zapier history does it appear that the triggered existed.

The attachment was made on the 21st and there was 1 trigger on that day, but not to that attachment.

I only received a no-reply e-mail from salesforce saying that a new case was attributed to you.

How did zapier did not find a trigger when this happened?

I use zendesk support and have an account on salesforce.

It could be that before adding an attachment, they should revert the case to me? 

Hi @rma 

To help us have more context, post screenshots with how your Zap steps are outlined and configured, thanks.

Hello, Troy, thanks for the reply. 

Here are how the steps are outlined:

 

However I found that the find ticket action was deprecated, that may have caused the problem - I fixed it and hopefully it will work in the future

Hi @rma! 👋 

Glad to hear you’ve potentially found the cause of the issue here. Hopefully switching from that deprecated version of the Find Ticket action has resolved things now. But if not or if you’re running into further trouble at all do let us know, happy to help! 🙂

Reply


Terms & Conditions