@Maddy
Probably best to open a ticket with Zapier Support for further troubleshooting assistance on this issue: https://zapier.com/app/get-help
@Troy Tessalone
It’s possible, although I’ve had this issue for two days, and if it was a straight connectivity issue then I would have expected it to impact all three zaps that share the same Xero connector. Most odd
@Maddy
FYI: Zapier is having an incident today that may be related: https://status.zapier.com/
Hi @Troy Tessalone Troy
Thanks for the response. I am aware of this approach, but as noted in my initial message, this has not resolved the problem. “I have tried re-connecting and have verified that the link to Xero is working, as is shown by the other two Zaps working fine”. So now I need an alternative solution.
Hi @Maddy
Good question.
The Xero account you're connecting with must have either Standard or Advisor level rights in order to use the Xero API, which is required for connecting with Zapier. Read-only, Invoice Only, and Cashbook Client roles don't have the ability to use the API.
This can happen if a second connection to Xero from the same account has taken place. If, under a separate Zapier account, you try to connect to the same organisation in Xero, this will replace the previous connection. To resolve, only connect your Xero account to one Zapier account.
Error: "Please re-connect your Xero account to Zapier on https://zapier.com/app/connections and try again."
You might see this error when you are testing your Zap, or when one of your live Xero Zaps tries to run.
This error usually happens because the authentication between Zapier and Xero stopped working. This could be because access was revoked inside of Xero, user permissions have changed, or the Xero tenant is no longer active.
- Go to https://zapier.com/app/connections
- Find the Xero authentication that stopped working
- Click the "Reconnect" button
- Follow the prompts in the pop-up to reconnect your account
- Once you successfully authenticate, turn on any Zaps that may have been turned off because of this error