# What does hubspot.engagement.logged prove?

> Prove that the engagement sits on the timeline of the deal. Version 1.0.0, certification Provisional.

Canonical: https://provely.sh/verify/hubspot/hubspot.engagement.logged  
Last reviewed: 2026-09-05  
Skill version: 0.1.0  
Certification: provisional  

**Prove that the engagement sits on the timeline of the deal. A note that exists is not a note on the deal. The level reads the note and the association to the deal that the person named.**

*Contract identity.*

| Fact | Value |
| --- | --- |
| Contract id | `hubspot.engagement.logged` |
| Version | `1.0.0` |
| Hash | `d4dc76168c09ea39` |
| Completion level | `logged` |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Skill | [HubSpot CRM API 0.1.0](/verify/hubspot) |
| Valid for provider API versions | `2026-03` |

## What is the intent?

Log this engagement against the deal.

## What is the subject and the action?

| Member | Value |
| --- | --- |
| Subject type | `hubspot.note` |
| Subject identity | note_id = `$action.result.id` |
| Canonical effect | `crm.engagement_log` |
| Provider operation | `POST /crm/objects/2026-03/notes` |
| Idempotency | none, retry is not safe |

## How does the evidence correlate with this operation?

| Strategy | Assurance | Keys | Required |
| --- | --- | --- | --- |
| `resource_id` | strong | note_id from `$action.result.id` | yes |
| `fingerprint` | weak | deal_id from `$input.deal_id`; hs_timestamp from `$input.hs_timestamp` | no |

## Which evidence does the contract require?

Minimum evidence level `E2`. An independent channel is required. Minimum channels: 1.

| Channel | Level | Independence | Verifier | Description |
| --- | --- | --- | --- | --- |
| `engagement_readback` | E2 | provider readback | `http` | Read the note with its deal associations. A condition path is $observed.engagement_readback.associations.deals.results. |
| `engagement_creation_events_in_account` | E3 | provider event | `webhook` | The object.creation notifications of the account since the operation started. The webhook verifier returns {events, count, latest, earliest, types, duplicates_dropped}. A count above one shows a second note. The published pages do not state which members the payload of a note creation carries. |

## Which conditions must all hold for VERIFIED?

| Condition | Meaning | Path | Operator | Expected | Evidence |
| --- | --- | --- | --- | --- | --- |
| `engagement_present` | The provider holds the note with the identifier of the answer. | `$observed.engagement_readback.id` | `eq` | `$action.result.id` | `engagement_readback` |
| `engagement_body_matches` | The text of the note equals the requested text. | `$observed.engagement_readback.properties.hs_note_body` | `eq` | `$input.hs_note_body` | `engagement_readback` |
| `engagement_created_in_window` | The provider created the note after the operation started. | `$observed.engagement_readback.createdAt` | `time_after` | `$operation.created_at` | `engagement_readback` |
| `engagement_linked_to_the_deal` | The note names exactly one deal, and that deal is the requested one. | — | `all_of` | The rows below state the members. | `engagement_readback` |
| `engagement_names_one_deal` |  | `$observed.engagement_readback.associations.deals.results` | `count_eq` | `1` | `engagement_readback` |
| `engagement_names_the_requested_deal` |  | `$observed.engagement_readback.associations.deals.results[0].id` | `eq` | `$input.deal_id` | `engagement_readback` |

## Which conditions give CONTRADICTED?

| Condition | Class | Reason | Path | Operator | Expected |
| --- | --- | --- | --- | --- | --- |
| `engagement_on_another_deal` | wrong subject | The engagement is associated with a different deal than the intent named. | `$observed.engagement_readback.associations.deals.results[0].id` | `ne` | `$input.deal_id` |
| `engagement_without_a_deal_association` | partial completion | HubSpot wrote the note and associated it with no deal. The engagement is not on the timeline of the deal. Ask a person. | `$observed.engagement_readback.associations.deals.results` | `count_eq` | `0` |
| `engagement_predates_operation` | pre existing state | The note is older than the operation. It proves nothing. | `$observed.engagement_readback.createdAt` | `time_before` | `$operation.created_at` |
| `duplicate_engagement_present` | duplicate side effect | HubSpot created more than one record in the account since the operation started. Do not retry. | `$observed.engagement_creation_events_in_account.count` | `gt` | `1` |

## Which observed states map to a verdict before completion?

| Rule | Match | Verdict | Reason |
| --- | --- | --- | --- |
| `engagement_archived` | `$observed.engagement_readback.archived` eq `true` | CONTRADICTED | The note is archived. It is not on the timeline of the deal. Ask a person. |

## How long does the runtime observe?

| Timing member | Value |
| --- | --- |
| Initial delay | 1000 ms |
| Poll interval | 5000 ms |
| Backoff | exponential factor 2, max 60000 ms |
| Maximum attempts | 40 |
| Timeout | 900000 ms |
| Stale read window | 20000 ms |
| On timeout | UNVERIFIABLE (`evidence_unavailable_before_timeout`), escalated to a person |

## Where do these rules come from?

- `hubspot.openapi#/paths/~1crm~1objects~12026-03~1notes/post`: [hubspot.openapi](https://api.hubspot.com/public/api/spec/v1/specs), retrieved 2026-09-08
- `hubspot.openapi#/paths/~1crm~1objects~12026-03~1notes/post/responses/201`: [hubspot.openapi](https://api.hubspot.com/public/api/spec/v1/specs), retrieved 2026-09-08
- `hubspot.docs.notes#notes/create-a-note`: [hubspot.docs.notes](https://developers.hubspot.com/docs/api-reference/latest/crm/engagements/notes/guide), retrieved 2026-09-08
- `hubspot.docs.notes#notes/associate-a-note-with-a-deal`: [hubspot.docs.notes](https://developers.hubspot.com/docs/api-reference/latest/crm/engagements/notes/guide), retrieved 2026-09-08
- `hubspot.openapi#/components/schemas/Note/properties/id`: [hubspot.openapi](https://api.hubspot.com/public/api/spec/v1/specs), retrieved 2026-09-08
- `hubspot.openapi#/paths/~1crm~1objects~12026-03~1notes~1{noteId}/get/responses/200`: [hubspot.openapi](https://api.hubspot.com/public/api/spec/v1/specs), retrieved 2026-09-08
- `hubspot.openapi#/components/schemas/Note/properties/properties`: [hubspot.openapi](https://api.hubspot.com/public/api/spec/v1/specs), retrieved 2026-09-08
- `hubspot.openapi#/components/schemas/Note/properties/createdAt`: [hubspot.openapi](https://api.hubspot.com/public/api/spec/v1/specs), retrieved 2026-09-08

### Can hubspot.engagement.logged return VERIFIED from the action response alone?

No. The minimum evidence level is E2. The action response is E1. The completion conditions read `engagement_readback`.

### What happens after the timeout?

The verdict is UNVERIFIABLE with the reason `evidence_unavailable_before_timeout`. The operation goes to a person for review.

## Read next

- [Read the HubSpot CRM API verification page](https://provely.sh/verify/hubspot)
- [Read the hubspot.deal.created contract](https://provely.sh/verify/hubspot/hubspot.deal.created)
- [Read the hubspot.deal.in_stage contract](https://provely.sh/verify/hubspot/hubspot.deal.in_stage)
- [Read what a completion contract contains](https://provely.sh/contracts)
- [Read what a receipt proves](https://provely.sh/docs/receipts)