our zapier account ran out of credits 3 days back and so we had to turn off all our existing zaps until it was renewed on friday !!! when i tried to enable the zaps today i was thrown an error:
Unable to refresh access token. Error code 400: {"error":"invalid_client_id","error_description":"client identifier invalid"} You should try reconnecting your Pardot account!
So understood it was related with pardot. when i went to zaps it was saying account has expired suddenly !!! then i tried to reconnect the zap with business ID but was again thrown with an error !!
could anyone help to rectify this scenario !!
Best answer by DanversBest answer by Danvers
Hi everyone!
I’m very pleased to report that this issue has now been resolved. The Pardot integration will now work as expected, but you will need to take the following actions in order to restart your Zaps:
2) Turn all Zaps connected to Pardot off and on again.
If you have Zaps that encountered an error during this issue, any associated Zap runs will not be able to be replayed. If you have data in your Zap Runs that cannot be replayed, and you would like to send that data through your workflow, you can export your Zap runs as a CSV by following these steps:
If you have any questions on how to do this, the best thing to do is to contact the Support Team using the Get Help form. They will be able to look at the data in your Zaps with you and can advise you on the best way forward.
@Danvers Sorry to keep poking you, but I would hope the team has scoped out the issue and has begun working toward a solution. Any update since yesterday?
We’re experiencing a similar issue that started last Friday. There was an interruption between our Pardot API & Zapier. We fixed the API issue but now none of our Pardot related zaps are successful; all of them have errored since 7/2 with the same error code as the original reporter:
Hey @SDC, @Barbie, @Jenelle, @Swati Malhotra, hope you are well!
This is the top priority bug for the Zapier engineering team right now. While I don’t have an ETA to provide on a fix, I can say that this bug is the #1 issue being address on our platform right now.
I’ve added all of you to the bug report notification list so that we can be sure to alert you ASAP once the issue is resolved. I apologize for the trouble here!
I don’t have an ETA but I can tell you that this is of the highest priority. We’ve identified what is likely the issue and are working on getting a fix in place. I have added you to the list of affected users, along with @david-lagos and @John.Radcliffe2 .
I don’t have an ETA but I can tell you that this is of the highest priority. We’ve identified what is likely the issue and are working on getting a fix in place. I have added you to the list of affected users, along with @david-lagos and @John.Radcliffe2 .
Please add us to the list of affected users too please, this is having a significant impact on our business.
Piling on. Noticed the error throw on Friday last week. I was hoping it was a config issue on my part. Please get fixed asap. This is impacting multiple MAPs programs and sales routings.
Hi, we’re facing the same issue here. Can you please get it fixed ASAP? It’s really important for our business, we might be loosing clients because of this!
We have identified the issue and are working to resolve it as quickly as possible but I’m afraid I don’t have a specific time estimate right now. I’ll post here when we’re able to get the issue resolved and you can also follow this status page for further updates.
In the meantime, I’m sorry again. I know that this means that any Pardot Zaps you have aren’t working and that that’s going to be frustrating for you. we’ll have another update for you soon.
we’ll have another update for you soon.