Hi @serial 

Good question.

You can add a Filter as Step 2 in the Zap: https://zapier.com/apps/filter/help

Hi @Troy Tessalone,

I’ve selected the subaccount already in the Trigger. Why would a filter needed then? 

It should then not trigger if the condition of the subaccount is not met. 

@serial

You can try reaching out to bunq Support as they likely created and manage their Zap app integration, which may have a bug that they would need to fix.

The Filter is a workaround, if the trigger is not working as expected.

I will reach out to Bunq and will post the followup here. Thank you. 

I’ve reached out to Bunq and they state that they did not make any changed on their side. 

In the meanwhile i have done some extra tests : 

1. Revoked Zapier access from all my accounts in Bun
2. Added Zapier again from only my sub account (not main account)
3. Saved the zap again with the newly enabled access from bunq
4. Made sure only the subaccount is selected in zap

Made test payment to sub account (should trigger) 

• result : not triggering

Second test : 

1. Revoked Zapier access from all my accounts in Bun
2. Added Zapier again including mainaccount
3. Saved the zap again with the newly enabled access from bunq
4. Made sure that only sub account is selected in zap

Made test payment to sub account (should trigger)

• result : payment on subaccounts triggers

Looking at data in: 

created 2023-09-26T10:00:05-0000

updated:2023-09-26T10:00:05-0000

monetary_account_id:6241739

Made test payment to main account (should not trigger)

• result : payment triggers zal

Looking at the data coming in, the correct account id is sent by bunq, but the zap should not trigger because of the selected sub account.: 

created:2023-09-26T21:57:42-0000

updated:2023-09-26T21:57:42-0000

monetary_account_id:1004657

Can you check / help?

@serial 

A Filter as Step 2 is a workaround, if the trigger is not working as expected.

Yes, i know, but adding a  filter would change this free zap for a limited project into a very expensive one.

Bunq in the meantime has replied and looking into the issue as they think it’s on their side .

Hello,

Bunq has reached out confirming it was a bug on the Bunq side.

They have fixed the bug, and i can confirm it's now working as expected, without extra filters.

That’s fantastic news @serial! Thank you for providing an update on this thread!

If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 

i just encountered this unexpected behaviour. is it possible it’s still not fixed?

(i’m now trying a filter)

Thanks for reaching out here, @excentric! 

I did some checking and couldn’t see any open bug reports matching this behaviour (we have an internal issue tracking tool that the bunq’s developers also have access to). I’d recommend reaching out to both the Zapier Support and bunq support teams to flag that this issue is occurring again. That’ll allow them to open up a new bug report for this issue so it can be investigated further.

In the meantime, adding that filter should help to prevent the Zap running for payments to the wrong sub-account. If you run into any trouble setting up the filter do let us know, happy to assist further.