Hi all,
wondering if anyone has any thoughts on this error i’m getting.
I had a zap that I’ve been using for months that takes an amount from my YNAB budget and automatically creates an expense in Splitwise. A week or two ago I started getting these errors every time I try and run it.
I’ve tried reformatting the amount to convert it to a currency and adding a dollar sign in front of it but nothing seems to be working.
Best answer by Danvers
View original
+14
Hi
Good question.
Can you provide the currency code used that resulted in the Zap step error?
versus the one i’m running now - seems to only be passing a few fields:
+14
If the currency code will always be the same, then you can set a static selection or value. (e.g. USD)
Otherwise, if you were mapped the currency code from the Zap trigger step, then check/test why that is no longer coming thru.
Or to prevent the errors, you can add a Filter step as step 2 to check that the Zap trigger included the currency code.
Returns a list of all currencies allowed by the system.
These are mostly ISO 4217 codes, but we do sometimes use pending codes or unofficial, colloquial codes (like BTC instead of XBT for Bitcoin).
I’ve never had to provide a currency code before. I tried running a zap from 6 months ago that worked without a problem.
next - i just multiply the amount by 2 and the final step is just sending it to split wise. There is no selection or input anywhere that asks for a currency code. I’ve also verified that the zap from 6 months ago that ran successfully, is now giving me the same error.
It seems as if Zapier is no longer retrieving or sending the same data as it used to?
As I mentioned, I tried adding a currency conversion where I change the amount to be in USD (which it will always be) and it still gave me the same error so I dont think it has to do with the number I’m passing
+14
Probably best to open a ticket with Zapier Support for help troubleshooting: https://zapier.com/app/get-help
+1 also experiencing this.
+1 on this issue.
+1 also having this issue
same issue here
+12
Hi everyone!
This looks like a bug that has popped up in the last few days. I’m sorry that it’s causing trouble with your Zaps and we’ll look into it as soon as possible.
Thanks!
FYI this is a bug caused by an unintended breaking change to Splitwise’s API which now requires `currency_code` to be provided (even though the docs don’t call out this parameter as required). They’ve said that a fix will be out shortly, but in the meantime if you provide `USD` as `currency_code` the requests should complete as before.
Looks like the Splitwise create expense task in my Zap just ran successfully, so with any luck the bug is fixed
+11
Thanks so much for sharing that information and helpful workaround here,
Glad to hear the Create Expense action is working correctly,
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
