ProvelyNo. HubSpot CRM API returns a success response when it accepts the request. Provely proves created, in_stage and logged as separate promises.
| Fact | Value |
|---|---|
| Skill version | 0.1.0 |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Last conformance run | 2026-09-05T12:00:00Z: 46 of 46 cases passed, 0 critical false VERIFIED |
| Provider API versions | 2026-03 |
| Default provider API version | 2026-03 |
| Compiled | 2026-09-05 |
| Manifest hash | 51408ddccc5bfcdd |
| Manifest hash check | the document hashes to the value the manifest states |
| Signature | valid, key provely-skill-2026-09, trusted by this build |
What does this page prove?
| Claim | Proven by | Evidence | Status |
|---|---|---|---|
| The record exists with the intended name in the intended pipeline. It does not prove the stage that the person asked for. Read the level in_stage for that. | hubspot.deal.created | E2 + E3 | proven |
| A created deal is not a deal in the right stage. HubSpot sets the stage from the create request, so another stage is a wrong value. | hubspot.deal.in_stage | E2 + E3 | proven |
| 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. | hubspot.engagement.logged | E2 | proven |
| An outcome outside HubSpot CRM API, such as a bank credit or a person who read a message | not proven | no E5 channel | not proven |
| The meaning of a HubSpot CRM API state that no source states | not proven | no source states it | not proven |
| The agent report that the action worked | never counts | E0 | not proven |
Which completion levels does the HubSpot CRM API skill expose?
Each level is one promise with one contract. An agent picks the level that matches the promise it makes. It cannot upgrade a level. Read the completion level definition.
| Level | Contract | Promise | Evidence | Certification |
|---|---|---|---|---|
created | hubspot.deal.created v1.0.0 | The record exists with the intended name in the intended pipeline. It does not prove the stage that the person asked for. Read the level in_stage for that. | E2 + E3 | Provisional |
in_stage | hubspot.deal.in_stage v1.0.0 | A created deal is not a deal in the right stage. HubSpot sets the stage from the create request, so another stage is a wrong value. | E2 + E3 | Provisional |
logged | hubspot.engagement.logged v1.0.0 | 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. | E2 | Provisional |
Which ways can a HubSpot CRM API action look done and not be?
| Contract | Case | Verdict |
|---|---|---|
| hubspot.deal.created | duplicate side effect | CONTRADICTED |
| hubspot.deal.created | pre existing state | CONTRADICTED |
| hubspot.deal.created | wrong amount | CONTRADICTED |
| hubspot.deal.created | wrong subject | CONTRADICTED |
| hubspot.deal.in_stage | duplicate side effect | CONTRADICTED |
| hubspot.deal.in_stage | pre existing state | CONTRADICTED |
| hubspot.deal.in_stage | wrong amount | CONTRADICTED |
| hubspot.deal.in_stage | wrong subject | CONTRADICTED |
| hubspot.engagement.logged | duplicate side effect | CONTRADICTED |
| hubspot.engagement.logged | partial completion | CONTRADICTED |
| hubspot.engagement.logged | pre existing state | CONTRADICTED |
| hubspot.engagement.logged | wrong subject | CONTRADICTED |
What did the last conformance run show?
The last conformance run on 2026-09-05T12:00:00Z passed 46 of 46 cases with 0 critical false VERIFIED. One critical false VERIFIED rejects a skill.
| Contract | Certification |
|---|---|
hubspot.deal.created | Provisional |
hubspot.deal.in_stage | Provisional |
hubspot.engagement.logged | Provisional |
The weakest contract is hubspot.deal.created. It reaches Provisional. The package level is Provisional, because a package level never rises above its weakest contract. Read the level of the contract you use.
| Case class | Passed | Total |
|---|---|---|
| duplicate side effect | 3 | 3 |
| error after execution | 3 | 3 |
| error before execution | 3 | 3 |
| evidence unavailable | 3 | 3 |
| pre existing state | 3 | 3 |
| stale readback | 3 | 3 |
| still transitional | 3 | 3 |
| terminal success | 4 | 4 |
| timeout after commit | 3 | 3 |
| version mismatch | 3 | 3 |
| webhook duplicate | 3 | 3 |
| webhook out of order | 3 | 3 |
| wrong amount | 2 | 2 |
| wrong subject | 4 | 4 |
| wrong terminal state | 3 | 3 |
The conformance artifact digest is c9281160c47982e2. The harness signs the run, so a reader can check that these numbers come from that run.
What remains uncertain?
The level is Provisional because of it. Provely does not guess a rule that a source does not state.
Where do these facts come from?
Every claim above cites a source assertion in the skill provenance. The compiler records the source, its hash, and the retrieval date. A page never states a provider rule without one.
| Source | Kind | Retrieved | Excerpt |
|---|---|---|---|
| hubspot.docs.deals | docs | 2026-09-08 | authored |
| hubspot.docs.notes | docs | 2026-09-08 | authored |
| hubspot.docs.versions | docs | 2026-09-08 | authored |
| hubspot.docs.webhooks | docs | 2026-09-08 | authored |
| hubspot.events | event sample | 2026-09-08 | authored |
| hubspot.openapi | openapi | 2026-09-08 | authored |
How do I verify a HubSpot CRM API action?
Verify a HubSpot CRM API action with Provely
- Begin the operation.Call
beginwith the contracthubspot.deal.createdand the input. Keep the operation id. - Make the HubSpot CRM API call you make today.Send the request with the correlation metadata that
beginreturned. - Submit the acknowledgement.Call
action_resultwith the HubSpot CRM API response. This is evidence level E1. It is not completion. - Verify.Call
verify. The runtime reads the evidence that the contract names, from HubSpot CRM API and not from the agent, and evaluates the contract. - Report the verdict exactly as returned.VERIFIED comes with a signed receipt. PENDING comes with the operation id. CONTRADICTED and UNVERIFIABLE are not success.
Questions developers ask
Does the created level prove the logged level?
No. The record exists with the intended name in the intended pipeline. It does not prove the stage that the person asked for. Read the level in_stage for that. 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. Use hubspot.engagement.logged to prove logged.
Which HubSpot CRM API API versions does the skill support?
2026-03. An operation on another version returns UNVERIFIABLE with the reason version_unsupported. The runtime never guesses.
Does Provely need write access to HubSpot CRM API?
No. The agent keeps its write key. The verifier reads with a separate read-only credential where HubSpot CRM API permits it, and it never shares that credential with the agent.