Connector Improvement: Brex 'Additional Travel Data' Fields Missing from Connector Schema
AnsweredHi Fivetran Support, we're requesting an enhancement to the Brex connector to include the "Additional travel data" fields that Brex displays on card transactions in their dashboard.
When viewing an airline transaction in the Brex app, there's an "Additional travel data" section under the Details tab showing Passenger Name and Ticket Number. These fields are completely absent from all 15 tables in the Fivetran Brex connector. We audited every table — the closest candidate, CARD_TRANSACTION_METADATA, only syncs custom key-value metadata, not the travel enrichment data.
This data likely comes from Level 2/Level 3 card network data that Brex receives on airline transactions. Brex clearly has it since they display it in their UI. We need these fields surfaced through the connector — either as new columns on an existing table or as a new table.
This is especially important for us because we use Egencia as our travel booking platform, not Brex Travel. So the Brex Travel module data isn't relevant to our workflow — we specifically need the card-level travel enrichment data (passenger name, ticket number) that Brex attaches to airline transactions regardless of where they were booked.
We're also raising this with Brex developer support in parallel. Happy to provide screenshots or participate in a beta.
Thank you,

-
Official comment
Hi Colin,
Thanks for this input. We are analysing this and will keep you posted as we make progress.
In the meanwhile, if you get any inputs from the Brex team on the APIs that will enable this, it would be a great help to expedite the process for us as well.
Regards,
Unni
Please sign in to leave a comment.
Comments
1 comment