Archive a batch of contacts
A documented HubSpot Contacts 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 a batch of contacts
- POSTChanges data · Batch
api.hubapi.com/crm/v3/objects/contacts/batch/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 HubSpot Contacts 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 HubSpot Contacts operations
- Create a contactPOST · changes data
- Search for contactsPOST · changes data
- Permanently delete a contact (GDPR-compliant)POST · changes data
- Archive a contactDELETE · changes data
- Update a contactPATCH · changes data
- Create a batch of contactsPOST · changes data
- Create or update a batch of contactsPOST · changes data
- Merge two contactsPOST · changes data
Questions
- Can HumDay archive a batch of contacts in HubSpot Contacts?
- Yes. This operation is published in HubSpot Contacts'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 HubSpot Contacts data?
- Yes — this is a POST operation, so it changes something in HubSpot Contacts. 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 HubSpot Contacts account.
Where this came from
Read from the API description HubSpot Contacts publishes themselves at api.hubspot.com/public/api/spec/v2/specs/release/22150/version/3. The description above is the provider’s own wording, not ours.