Flag Person as Incorrect
clearbit.flag_person
ActionCRM & salesconnection required
Calls the Clearbit API with the connection's credentials.
Report that a person record is wrong, optionally sending Clearbit the corrected attributes so future lookups improve.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Clearbit
- Secret shape
- the secret API key (sk_…), or {"api_key": "…"}
- Config it needs
- stream, suppression, webhook_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 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 |
|---|---|---|---|---|---|
person_id The Clearbit id of the person to flag. | string | Yes | — | — | — |
corrections Corrected attributes as JSON, for example {"given_name": "Alex", "twitter_handle": "alexmaccaw"}. | object | No | — | — | {"given_name":"Alex","twitter_handle":"alexmaccaw"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"corrections": {
"given_name": "Alex",
"twitter_handle": "alexmaccaw"
}
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
flagged True when Clearbit accepted the report. | boolean | — |
person_id The person id that was flagged. | string | — |
response Clearbit's acknowledgement body. | object | — |
{
"flagged": false,
"person_id": "",
"response": {}
}Solutions with Clearbit
See Flag Person as Incorrect run in a workflow.
In a technical demo we add the Clearbit connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.