Annotate Assessment
recaptcha_enterprise.annotate_assessment
ActionGoogle Cloudconnection required
Calls reCAPTCHA Enterprise POST assessments/{id}:annotate.
Annotate a previous assessment as legitimate/fraudulent to tune the model.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google reCAPTCHA Enterprise
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, site_key
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
assessment Assessment name (from create_assessment). | string | Yes | — | — | — |
annotation Outcome — reCAPTCHA Enterprise accepts only the listed values. | string | No | LEGITIMATE | one of "LEGITIMATE", "FRAUDULENT", "PASSWORD_CORRECT", "PASSWORD_INCORRECT" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"annotation": "LEGITIMATE"
}Input
Used when the config leaves assessment blank.
| Field | Type | Example |
|---|---|---|
name Assessment name, as emitted by recaptcha_enterprise.create_assessment. | string | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
assessment | string | — |
annotation | string | — |
{
"annotation": "",
"assessment": "",
"ok": false
}Related Google reCAPTCHA Enterprise nodes
See Annotate Assessment run in a workflow.
In a technical demo we add the Google reCAPTCHA Enterprise connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.