Connector Improvement: Linear Connector is Missing Customer and CustomerNeed tables
AnsweredHi Fivetran Team,
Your linear connector is missing two key tables in Linear: Customer and CustomerNeed.
Can you update the connector to included these two tables in the schema?
https://linear.app/developers/managing-customers
-
Official comment
Hi Mason,
Thank you for reaching out and sharing your thoughtful suggestion with us. We appreciate your engagement and are excited to let you know that we have already planned to update the Linear connector to include the Customer and CustomerNeed tables in the schema.
Our development team is currently working on this enhancement, and we expect it to be completed and available soon. We believe this update will significantly enhance your experience and provide greater insights through our connector.
Thank you once again for your valuable input. Please feel free to reach out if you have any more suggestions or need further assistance.
Best regards,
Syead Mujtaba Imam Rizwi -
Also, we need a table that links projects and issues to customers. So a customer id on the project and issue tables. Or a project / issue to customer mapping table.
-
The current Fivetran Linear schema is missing the Customer Requests data model introduced by Linear. Linear’s GraphQL API exposes two objects:
Customer (companies; fields include id, name, plus optional domains, externalIds, revenue, size, tierId)
CustomerNeed (customer requests; fields include issueId, customerId, priority, body, etc.), which links to Issue and optionally to Customer.
Reference docs:
- Managing Customers (Linear Devs): https://linear.app/developers/managing-customers
- Customer Requests overview: https://linear.app/docs/customer-requests
- GraphQL schema (public explorer/examples): https://studio.apollographql.com/public/Linear-API/variant/currentFivetran’s current Linear connector syncs ISSUE, LABEL, PROJECT, TEAM, etc., but does not include Customer or CustomerNeed, nor the Issue → CustomerNeed → Customer relationships. This prevents us from joining issues to customer requests, or running customer-level analytics (e.g., requests by tier, revenue, size).
Without Customer & CustomerNeed, we cannot reproduce Linear’s “Customer Requests” reporting in our warehouse, which blocks prioritization dashboards and ROI analyses tied to named customers and tiers.
Please sign in to leave a comment.
Comments
3 comments