Connector Improvement: Intercom Article Endpoint fields
AnsweredWe observed Article object from Intercom Connector is missing few fields like
- parent_id
- parent_ids
As listed here
https://developers.intercom.com/docs/references/rest-api/api.intercom.io/articles/article
It helps to bridge article parent-child relationship
Also we like to get help_center_id exposed associated with each Article_id as listed here
https://developers.intercom.com/docs/references/rest-api/api.intercom.io/articles/searcharticles
Can we get these enabled for Intercom connector to utilize Fivetran for this.
-
Official comment
Hi Ramki,
Thanks for raising this request.
We’ve added this request to our near-term backlog and will share updates as we make progress.
On tracking deleted articles, could you share a bit more about your use case or what problem you’re trying to solve with this?
Thanks,
Vignesh R -
Also can we get a way to track/flag deleted articles. (i.e Articles deleted in Intercom and not in Snowflake(destination) should be flagged with _fivetran_deleted column.
-
Hi Vignesh
In Intercom help center folks maintain Articles and over the period of time they would remove them as they get irrelevant. So if an article_id that came in on day 1 via Fivetran replication and no longer available in future we need to flag that deleted article_id row with _fivetran_deleted flag so users would know in Snowflake destination on list of deleted articles.
Thanks
Ramki
-
Thanks Ramki for clearly outlining your use case. We’ll include this in our roadmap and keep you posted once it’s implemented.
Please sign in to leave a comment.
Comments
4 comments