Community

Feature Requests

New post

Share your ideas for improving Fivetran. Upvote existing requests to help our team set priorities, or create a new request if you have a new idea. Your ideas will be organized, appreciated and thoughtfully considered. Someone from Fivetran will respond to your request.

All Planned Not planned Completed Answered No status Newest post Recent activity Votes Comments
New Destination: SFTP - Upload data Completed
  • Jai Gohil
5
New Connector: Sage 50 Responded
  • Chandrasekar Rajendran
0
Connector Improvement: Avoid Manual Reconnection for the connector
  • Atishi Gupta
3
Other: General improvements for records syncs in Snowflake destinations Responded
  • Joao Lisboa
0
Connector Improvement: Enable new fields in Charge object in Coupa Completed
  • Ketan Unkule
3
Connector Improvement: Add daily performance report for Impact connector Planned
  • Suhas M G
1
Connector Improvement: Add Tables to the Xaclty Connector Completed
  • Daniel Gomez
0
Connector Improvement: Klaviyo - Mobile Push Notification Enabled Responded
  • Amit Tiwari
0
Connector Improvement: Calendly Connector to Support Zoom Responded
  • Macklin Fluehr
0
Connector Improvement: MongoDB: Add ability to avoid duplicate column name clashes Responded
  • Robert Bramwell
1
Connector Improvement: Request to Add Jira Issue Votes API Call Completed
  • simon kienesberger
0
Dashboard Improvement: Enhance Connector Schema UI to Allow Searching by Column Name
  • Roni Ström
1
Connector Improvement: Enhance HVA Connector to Retrieve Additional Metadata from DB2 i Journal Entry Data (e.g., CURRENT_USER and ENTRY_TIMESTAMP) Responded
  • Roni Ström
0
New Connector: Shopify Return Data Completed
  • Kathy (Qiuye) Liu
1
New Destination: Need new Oracle destination for our project Completed
  • R Durga Prasad Velpuri
2
Destination Improvement: Optimize the queries written by HVR to load data to Google BigQuery Planned
  • Samyak jain
0
Dashboard Improvement: Create granular Connector level role
  • Saurabh Vaish
2
Other: Two or more groups in one channel with different set of tables causes F_JR0225 during replication activation.
  • Rafał Stajkowski
0
Connector Improvement: mTLS support for PostgreSQL connector Responded
  • Tom Mitchell
0
Destination Improvement: Array Support for BigQuery, Snowflake, etc.
  • Alex Daley
0
Connector Improvement: add some additional key reports to amazon selling partner api Responded
  • Esteban Angel
1
Connector Improvement: Shopify B2B Catalogs and Companies Assigned To Responded
  • Daniel Santamaria Beltran
0
Connector Improvement: Add Sponsored TV ads to the Amazon Ads connector Responded
  • Will Holtz
1
Connector Improvement: Snowflake Connector Improvement - Feature flag to compute _fivetran_id on fivetran for non-cdc connectors Not planned
  • Joel Santiago
0
Destination Improvement: Add account-level ID 'key' column across paid search and social connector tables Not planned
  • Sam Poelstra
  • Edited
5
Connector Improvement: Resource Management by Smartsheet Responded
  • Sean Whinnie
2
Connector Improvement: Facebook Ads - Add canvas and canvas_elements dimension tables Responded
  • Florian Chabert
0
New Connector: Priority Responded
  • Rishabh Shah
1
New Connector: e2Open TA (Tradesphere previously) Responded
  • Rishabh Shah
1
New Connector: GTreasury Responded
  • Rishabh Shah
1