Archive contact in Intercom
A documented Intercom operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Archive contact
- POSTChanges data · Contacts
api.intercom.io/contacts/{contact_id}/archive
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Intercom operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Intercom operations
- Create a ticketPOST · changes data
- Create contactPOST · changes data
- Create a messagePOST · changes data
- Add subscription to a contactPOST · changes data
- Merge a lead and a userPOST · changes data
- Create event summariesPOST · changes data
- Create or update a tag, Tag or untag companies, Tag contactsPOST · changes data
- Submit a data eventPOST · changes data
Questions
- Can HumDay archive contact in Intercom?
- Yes. This operation is published in Intercom's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Intercom data?
- Yes — this is a POST operation, so it changes something in Intercom. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Intercom account.
Where this came from
Read from the API description Intercom publishes themselves at raw.githubusercontent.com/intercom/Intercom-OpenAPI/main/descriptions/2.11/api.intercom.io. The description above is the provider’s own wording, not ours.