Skip to main content
Question

Difficulty Integrating NBAD Bank Balance Inquiry with Pipefy Automation

  • February 26, 2026
  • 1 reply
  • 24 views

Hi everyone,

I am currently trying to automate a daily bank balance inquiry from our corporate account with First Abu Dhabi Bank into Pipefy so our finance team can track cash position directly inside a pipe. The idea is to automatically create or update a card every morning with the latest available balance, instead of someone logging into the bank portal and manually updating the information.

We are on the Enterprise plan and started testing this through the Integration Hub using an HTTP request to the bank’s API. The issue is that even though the API call works in Postman with the same credentials, inside Pipefy the request either times out or returns an authentication error. We have double checked the headers, tokens, and IP restrictions, and from the bank’s side they confirmed the credentials are valid.

Another challenge is that even when we simulate a successful response, I am not sure about the best way to structure the data so that the balance history is stored properly for reporting. Should we update the same card daily or create a new card per day to keep a historical record for dashboards?

Has anyone here integrated a UAE bank balance inquiry into Pipefy before, especially with FAB or another local bank? I would really appreciate guidance on handling authentication securely inside the platform and best practices for storing financial snapshot data for reporting purposes.

1 reply

joao-quint
Pipefy Staff
Forum|alt.badge.img+6
  • Pipefy Staff
  • February 27, 2026

Hi ​@paprone , welcome to the community!

For the authentication and timeout issue specifically, I’d strongly recommend reaching out to Pipefy Support via the in-app chat. If you can share the pipe ID and the automation ID, the support team can check the execution logs on our side and pinpoint exactly where the request is failing (timeouts, blocked IPs, auth headers, TLS, etc.). That usually leads to a much more accurate and faster resolution than trial and error.