Skip to main content

Hi everyone. I’ve set up a Zap to send new payments in my Bunq account to YNAB. This was working almost fine, although it would occasionally trigger twice for the same new payment. Howeverm, since introducing an additional two Bunq accounts, each of the payments are trigger twice or sometimes three times. Payments are therefore appearing in YNAB multiple times.

 

Interestingly, the new payments are being found by Zapier at completely different times, but Zapier is not recognising that they are in fact the same payment. Screenshots included below of the same payment being found at different times 

 

 

Hi @Mjelwo 

Can you post more screenshots showing the same Zap trigger data across different Zap Runs?

https://zapier.com/app/history/


This post has been edited by a moderator to remove personal information. Please remember that this is a public forum and to remove any sensitive information prior to posting.

Sure. Here’s the data from one run:
-------

id:

xxxxx03184

created:

2024-07-16T11:23:48-0000

updated:

2024-07-17T03:05:33-0000

monetary_account_id:

xxxx351

amount:

currency:

EUR

value:

-20.34

description:

xxxxxx xxxxx xxxx AMSTERDAM, NL

type:

MASTERCARD

alias:

iban:

NL46BUNQ

is_light:

false

display_name:

 

avatar:uuid:

9574f34d-0f55-4f4f-b38e-8ba8580fc621

image:0:attachment_public_uuid:

93aebb08-ea66-4e76-858c-9cfe4d437b62

height:

1024

width:

1024

content_type:

image/jpeg

urls:0:type:

ORIGINAL

url:

https://bunq-prod-model-storage-public.s3.eu-central-1.amazonaws.com/bunq_file/File/content/5d1f52eb90384911df469c2b07e771672858b4a04a1be4581958093d6af9700d.jpg

anchor_uuid:

null

style:

NONE

label_user:uuid:

70c98dbe-7c78-48e8-bffd-47eed6c84b61

display_name:

 

country:

NL

avatar:uuid:

6c533558-ec03-4a5a-b522-809e98899da5

image:0:attachment_public_uuid:

2a79c91c-3f00-4ead-99f3-854453bf8706

height:

640

width:

640

content_type:

image/png

urls:0:type:

ORIGINAL

url:

https://bunq-prod-model-storage-public.s3.eu-central-1.amazonaws.com/bunq_file/File/content/e627dab1418debb69a8ab983e7cd99a7b0cb8c289892dde90a8b2f12d5e23140.png

anchor_uuid:

70c98dbe-7c78-48e8-bffd-47eed6c84b61

style:

NONE

public_nick_name:

xxxxxx

type:

xxxxx

country:

NL

counterparty_alias:

iban:

null

is_light:

null

display_name:

xxxxx xxxxx 1497

avatar:uuid:

6c6875e0-c5de-4983-bb58-fa218d6fff3c

image:0:attachment_public_uuid:

97832b3d-654d-4184-a457-335bf3adf390

height:

640

width:

640

content_type:

image/jpeg

urls:0:type:

ORIGINAL

url:

https://xxxxxxxxxx1.amazonaws.com/bunq_file/File/content/e8016c0c2040edaa3af4f2a7fb215503482be6687b4c58ab45170eed674960ec.jpg

anchor_uuid:

null

style:

NONE

label_user:uuid:

null

display_name:

xxxxxx xxxx 1497

country:

NL

avatar:

null

public_nick_name:

xxxxxx xxxx 1497

type:

null

country:

NL

merchant_category_code:

xxxx

sub_type:

PAYMENT

payment_arrival_expected:

status:

ARRIVED

time:

null

balance_after_mutation:

currency:

EUR

value:

192.44

Fields with no value:

merchant_reference

attachment

geolocation

batch_id

scheduled_id

address_billing

address_shipping

request_reference_split_the_bill

payment_auto_allocate_instance

payment_suspended_outgoing

 

And here’s the data from a second run:

id:

1614803184

created:

2024-07-16T11:23:48-0000

updated:

2024-07-16T11:23:48-0000

monetary_account_id:

9419351

amount:

currency:

EUR

value:

-20.34

description:

xxxxxx xxxxx xxxx AMSTERDAM, NL

type:

MASTERCARD

alias:

iban:

 

is_light:

false

display_name:

 

avatar:uuid:

9574f34d-0f55-4f4f-b38e-8ba8580fc621

image:0:attachment_public_uuid:

93aebb08-ea66-4e76-858c-9cfe4d437b62

height:

1024

width:

1024

content_type:

image/jpeg

urls:0:type:

ORIGINAL

url:

https://bunq-prod-model-storage-public.s3.eu-central-1.amazonaws.com/bunq_file/File/content/5d1f52eb90384911df469c2b07e771672858b4a04a1be4581958093d6af9700d.jpg

anchor_uuid:

null

style:

NONE

label_user:uuid:

70c98dbe-7c78-48e8-bffd-47eed6c84b61

display_name:

x.x. Marcus

country:

NL

avatar:uuid:

6c533558-ec03-4a5a-b522-809e98899da5

image:0:attachment_public_uuid:

2a79c91c-3f00-4ead-99f3-854453bf8706

height:

640

width:

640

content_type:

image/png

urls:0:type:

ORIGINAL

url:

https://bunq-prod-model-storage-public.s3.eu-central-1.amazonaws.com/bunq_file/File/content/e627dab1418debb69a8ab983e7cd99a7b0cb8c289892dde90a8b2f12d5e23140.png

anchor_uuid:

70c98dbe-7c78-48e8-bffd-47eed6c84b61

style:

NONE

public_nick_name:

xxxxx

type:

xxxxx

country:

NL

counterparty_alias:

iban:

null

is_light:

null

display_name:

xxxxxx xxxxx 1497

avatar:uuid:

6c6875e0-c5de-4983-bb58-fa218d6fff3c

image:0:attachment_public_uuid:

97832b3d-654d-4184-a457-335bf3adf390

height:

640

width:

640

content_type:

image/jpeg

urls:0:type:

ORIGINAL

url:

https://bunq-prod-model-storage-public.s3.eu-central-1.amazonaws.com/bunq_file/File/content/e8016c0c2040edaa3af4f2a7fb215503482be6687b4c58ab45170eed674960ec.jpg

anchor_uuid:

null

style:

NONE

label_user:uuid:

null

display_name:

xxxxx xxxx 1497

country:

NL

avatar:

null

public_nick_name:

xxxxxx xxxxx 1497

type:

null

country:

NL

merchant_category_code:

5411

sub_type:

PAYMENT

payment_arrival_expected:

status:

HIDDEN

time:

null

balance_after_mutation:

currency:

EUR

value:

192.44

Fields with no value:

merchant_reference

attachment

geolocation

batch_id

scheduled_id

address_billing

address_shipping

request_reference_split_the_bill

payment_auto_allocate_instance

payment_suspended_outgoing

 

Im observing now that the payment status differs in the two transactions, so I imagine one solution would be to use a filter to filter out payments that haven’t arrived. But this isn’t ideal for a few reasons, amongst them: only transaction that have been completed would show up in YNAB, and it would turn this Zap into a multi-step zap. Pro plans are a tad expensive when Im only running a handful of very simple zaps...


@Mjelwo 

Seems like a Filter would be the right approach.

 


Reply