Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to query contact id when contact is archived? #599

Open
ryan-kim-siteminder opened this issue Dec 7, 2022 · 1 comment
Open

How to query contact id when contact is archived? #599

ryan-kim-siteminder opened this issue Dec 7, 2022 · 1 comment

Comments

@ryan-kim-siteminder
Copy link

ryan-kim-siteminder commented Dec 7, 2022

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 get it used as a prameter for deleting contact permanently? FYI, this requirement is part of PII(Personal Identifiable Information) initiative.

Version info

  • intercom-ruby version: v3.1.4
  • Ruby version:

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.

@SeanHealy33
Copy link
Contributor

Hello @ryan-kim-siteminder I've looked into this unfortunately our API does not have a way to search for archived contacts yet. The API will return the contact if you've the specific id of the archived contact. I've raised this issue with the Contacts API feature team to implement in future roadmaps.

We do have a webhook topic contact.archived that you can use to track if a contact is archived for later deletion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants