Triggering an entry into YNAB when a new transaction is added to Splitwise not creating an expenses
I’m trying to set up a Zap that triggers an entry into YNAB when a new transaction is added to Splitwise. I’ve set it up so the trigger is the Splitwise entry and the action is entering it into YNAB, but it’s not creating an expense in YNAB.
Any help or suggestions welcomed!
Page 1 / 1
Hi @sdiamond7
Good question.
Please post screenshots with how your Zap step is configured in order for us to have more context, thanks.
Here’s a screenshot that walks all the way through the Zap. My guess is that there’s an error exporting the expense from Splitwise resulting in an inability to categorize or place it in YNAB, but that’s just a guess.
Make sense. BUT the value entered for each Splitwise entry will be different; is there a way to indicate that the value will change or does it need to be fixed for this Zap to work?
The test action works, but not any subsequent entries. Any ideas?
@sdiamond7
Check your ZapRuns to see the DATA IN/OUT for each step to help troubleshoot once you’ve turned the Zap ON and tested live: https://zapier.com/app/history/
FYI: Zaps work while turned ON for new data going forward.
With a polling trigger, Zapier will check for new data from your trigger every 1 to 15 minutes in order to start your Zap, depending on your pricing plan.
Hi friends! I wanted to pop in and summarize some of these responses in case it’s helpful.
Troy mentioned the amount field needing to be a number value.
As a troubleshooting step if the test action isn’t quite working they recommend this:
Check your ZapRuns to see the DATA IN/OUT for each step to help troubleshoot once you’ve turned the Zap ON and tested live: https://zapier.com/app/history/
FYI: Zaps work while turned ON for new data going forward.
With a polling trigger, Zapier will check for new data from your trigger every 1 to 15 minutes in order to start your Zap, depending on your pricing plan.