[source-intercom] field types for tags and contacts on stream conversations does not match manifest definition

[juoll-data]

Connector Name

intercom

Connector Version

0.12.1

What step the error happened?

Updating the connector

Relevant information

After upgrading the connection to version 0.12.1 and then updating the schema :

• the field tags for stream conversations still appear as a simple object. Nested fields like id, type or name does not appear as it should regarding the manifest : https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/connectors/source-intercom/manifest.yaml#L2151

• the field contacts for stream conversations still appear as a simple object. Nested fields like id, type or external_id does not appear as it should regarding the manifest : https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/connectors/source-intercom/manifest.yaml#L1722
  

Relevant log output

Contribute

• Yes, I want to contribute

[marcosmarxm]

@btkcodedev can you take a look at this issue?

[btkcodedev]

Yep, on it

[juoll-data]

Let me know if i should open an issue for this. But for the same connector version, I observed that the field assignee on stream conversations is not being populated.

[btkcodedev]

Will do this update after this PR is merged, #53187

[juoll-data]

Actually, assignee on stream conversations should not be in the manisfest anymore as the connector is using the intercom api version 2.11. Now, team_assignee_id and admin_assignee_id are used instead and are currently correctly populated by the connector. Sorry for the misunderstood and thank for your quick reaction to this issue.

[juoll-data]

I updated the description.