Can the Tableau adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Tableau tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Tableau adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
Do we own the integration code at the end?
Yes. The Connectify Tableau adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.
What happens if Tableau changes their API after we go live?
Our SRE team monitors Tableau change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
Is this a packaged Tableau connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for New York City, New York. After go-live, the Tableau adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.