Trelica (1Password SaaS Manager) connector — add application_id, description, and vendor.id fields
AnsweredConnector name: trelica
Table name: application_role_member, application
Column to add: application_role_member.application_id, application.description, application.vendor_id (from the nested vendor.id field)
API documentation link: https://www.postman.com/trelica/1password-saas-manager/documentation/8ckliux/1password-saas-manager-api?entity=request-12223689-f8c90ae6-0a67-430c-8396-30eafe409cb6&sideView=agentMode
Reason: application_role_member currently has no way to identify which application a role assignment belongs to — the only other key on the table, application_role_index, is not globally unique (it repeats across hundreds of different applications), so this table is effectively unusable for reporting App Owner / Budget Owner / Procurement Manager / SME assignments per app. description and vendor.id are both present in the same API response the connector already calls but aren't currently mapped — vendor.id in particular would give us a stable join key instead of relying on inconsistently formatted vendor name text.
Impact: This data supports SaaS vendor renewal research, contract/spend reconciliation, and vendor ownership reporting across our procurement pipeline — without these fields we can't reliably attribute app ownership or build a stable vendor dimension for cross-system analysis.
-
Official comment
Hi Matthew,
Thank you for submitting your feature request for the Trelica connector.
We are currently assessing customer demand and will begin a detailed feasibility analysis to determine the viability of building and maintaining a high-quality Fivetran connector for Trelica. The request has been added to our backlog, and as we progress through our evaluation, we may reach out for additional details to ensure the solution aligns closely with your requirements and expectations.
We appreciate your feedback and continued support - it plays an important role in shaping our product roadmap.
Best regards,
Sahu -
Hi Sahu,
Thank you for your reply! I just wanted to clarify that the connector already exists. The request is to include a few additional columns in the model that are readily available through the Trelica API payloads. One of these columns being missing (application_id on application_role_member) currently blocks the application_role_member table from used for it's purpose. I hope this clarifies the scope of this request. Let me know if I can provide any additional information.
Best,
Mathew
Please sign in to leave a comment.
Comments
2 comments