• Zapier trigger not honoring sub-account setting

Hello,

I've created a zap on Zapier, with a real simple Bunq integration :

  • Incoming payment on subaccount
  • Insert row on Google Docs

But the zap is also triggering on all my other accounts.

According to Zapier I need to reach out to Bunq to check this out because i might be a Bunq bug.

    @Silvester-Yellow-Bear#282996 Hey there, Silvester πŸ‘‹ Thanks for reaching out to us! If you've run into an issue with a Zapier integration, you can reach out to our dedicated team at apipartner@bunq.com for assistance 🌈

      Hello, i've sent the e-mail to the dedicated team. No response though.

        Hey @Silvester-Yellow-Bear#283298 πŸ‘‹
        We sincerely appreciate your patience as we work to address your inquiry. Our API support team is diligently reviewing and responding to emails, but due to high demand, there may be a slight delay in their response time.

        Rest assured, we're committed to providing you with the best assistance possible, and we kindly ask for your understanding as we strive to deliver a thorough and timely response to your email within the next few days πŸ™

          13 days later

          Hello @sotirios-Black-Moose#283299

          I understand that there is a high demand for the team, but 2 weeks further i've still not heard anything from the team, and the Zappier is still not filtering from the correct subaccount (all accounts trigger)

          Can you maybe sent a message internal to ask when i can expect a reply?

          Cheers and have a nice day!
          Silvester

            @Silvester-Yellow-Bear#283800 Hello Silvester πŸ‘‹

            Thank you for reaching out again, we appreciate your patience. We understand the importance of resolving this matter for you, and we're committed to getting it sorted out as soon as possible.

            Please bear with us a little longer, we're working diligently to address your concerns.

            Thank you for your understanding, and have a wonderful day 🌈

              a month later

              Hello,

              The API team reached out and they confirmed that the bug is fixed now, i've tested it and also can confirm this bug is fixed now.

              Cheers.

                Write a Reply...