Give the next conversation its context.

Contact matching normalizes identifiers and refuses ambiguous results. Two matching contacts are a decision for a person, not permission to merge records or take the first search result.

This protects the relationship between an enquiry and its customer. A failed or ambiguous match should be reviewed before further action is treated as complete.

The implemented activity body contains a short summary and a link back to Evarmont. Transcript access stays in the authenticated dashboard, where the organization’s roles and retention rules apply.

Evarmont records completed operation references to protect normal replays. HubSpot does not provide a universal write-idempotency guarantee for these activities, so uncertain external results still need careful recovery.

Connect the intended HubSpot account through OAuth. HubSpot has no additional calendar or channel selection step in Evarmont. An organization or location binding chooses the CRM connection used by a workflow.

Access to read and write CRM contacts and the permissions required for the declared contact and activity operations. The consent grant is checked against the operations the connection needs.

Contact-change webhook handling verifies HubSpot’s signature and timestamp before deduplicating the event. An inbound change is scoped to the existing provider subscription and connection.

Disconnecting stops new CRM operations in Evarmont. To remove the provider installation, use HubSpot’s connected-apps controls. Contacts and activities already written are not erased by disconnecting.