Update Freschat Tables (conversation_property, conversation_property_choice) with ability to join to conversation_id
Answered
Additional details:
There are two tables (conversation_property, conversation_property_choice) that are able to be joined to each other, but no other tables. Information is not usable unless there's the ability to join to the conversation table and others to pull details such as create date, user, agent, etc.
This data is required to capture essential bot disposition data stored in conversation_property. Below is a screenshot of API data where a relationship between these tables is demonstrated:
-
Official comment
Hi Jonathon,
Thank you for submitting your feature request for the Freshchat 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 Freshchat. 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.
In the meantime, could you briefly share your primary use case for this feature? We would also like to know, along with conversation_property, which other tables you would like to join these tables to?We appreciate your feedback and continued support - it plays an important role in shaping our product roadmap.
Best regards,
Sahu
Please sign in to leave a comment.
Comments
1 comment