Skip to main content

I’m trying to move a project (opportunity) along in Copper after a trigger. For some reason if I choose a stage, I get a 422 error. If I leave that blank, it succeeds. These are values that are directly fetched from Zapier/Copper, so I don’t know why it would fail. I tried choosing the pipeline + stage, and tried just the stage, both fail. But without the stage, it succeeds, and can update other values. Any thoughts on this? Anyone else using Zapier to move things through their pipelines?

 

With no stage selected, it succeeds.
With stage selected it fails. I tried manually entering the stage ID, that fails as well.
Pipeline & Stage are chosen from the list that populates automatically, from our Copper account.



Thanks!

 

Hi there @MattVS,

Welcome to the Community! 🎉

I did some digging into this, and it seems like the error you’re running into is a known bug with the Copper integration. Our team is aware of the issue and we're working with Copper on a fix. I've added your email address as another affected member. That does a few things:

  • Bring this to the attention of the integration developers
  • Help track and prioritize fixes
  • Allows us to notify you via email if/when this is fixed

Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.

Additionally, I recommend reaching out to the Copper dev team and let them know that you’re running into a bug with their app in Zapier since they are the one who maintain and update their bug in Zapier.

I appreciate your patience and understanding.


Any update to this Error 422…..I am having the same issue


Hi ​@gerodea,

It looks like the bug report is still open. In the meantime, I have added you as a another affected member of the bug. We will keep you updated via email once the bug has been fixed.

I appreciate your patience and understanding.


Any Updates to this. I am also having trouble with this. Can you also add as an affected member

This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing sensitive details.


Thanks for reaching out here, ​@Mariella! I’ve checked on the bug report and there’s no updates on it’s status unfortunately. I’ve added you to the list of folks being affected so we can notify you by email as soon as the developers of the Copper app get this sorted.

As a workaround, I wonder if it might be worth trying a Custom Action or and API Request to update the opportunity instead? If you’ve not used those kind of actions before you can learn more about how to use them here:


Hope that helps. If you give either of those a try and run into any issues, let us know and we’ll be happy to assist! 🙂


Hi I tried the custom action and it didn’t work properly with copper. Is there any update on this bug by chance?


Hi ​@scout,

Unfortunately, the bug is still open. I have added you as another affected member. We will keep you updated once the bug has been fixed.

Additionally, I recommend for you to reach out to the Copper support team directly as well since they are the one who owns the integration in Zapier.

I appreciate your understanding.