You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To delete archived contact permanently, we need to use contact id but it seems to me that there is no way we can retrieve contact id if contact is archived. Is there any way I can retrieve contact id to use it as a parameter for deleting contact permanently? FYI, this requirement is part of PII(Personal Identifiable Information) initiative.
Version info
version: v3.1.4
Expected behavior
There should be a way to retrieve contact id for archived user. So archived users can be deleted permanently.
Actual behavior
I want to use email to search contact id for archived user but intercom api client does not provide that.
Tried to unarchive contact to get the contact id but to no avail because to unarchive contact it needs contact id.
The text was updated successfully, but these errors were encountered:
Same issue here. I need to unarchive contact but I can't because I don't know their intercom id (I know the external_id and other fields but not the one provided by Intercom). I am finding no way to search archived contacts so I can get their intercom id and unarchive them.
To delete archived contact permanently, we need to use contact id but it seems to me that there is no way we can retrieve contact id if contact is archived. Is there any way I can retrieve contact id to use it as a parameter for deleting contact permanently? FYI, this requirement is part of PII(Personal Identifiable Information) initiative.
Version info
Expected behavior
There should be a way to retrieve contact id for archived user. So archived users can be deleted permanently.
Actual behavior
I want to use email to search contact id for archived user but intercom api client does not provide that.
Tried to unarchive contact to get the contact id but to no avail because to unarchive contact it needs contact id.
The text was updated successfully, but these errors were encountered: