HEherondata

Ingest end user data from a CRM webhook

Changed on

Receives a webhook payload from a CRM integration and syncs the end user via the ingestion pipeline. Per-CRM payload shapes are parsed by the matching CRM client; only the generic ingestion controls documented below are read directly here.

post/api/ingestion/crm/{crm_integration_heron_id}

Request

  • Base URL
    https://app.herondata.io
  • URL
    https://app.herondata.io/api/ingestion/crm/{crm_integration_heron_id}
  • Auth
    API key in header x-api-key

Path parameters

crm_integration_heron_idstring required

Heron ID of the CRM integration

Request body

start_workflowboolean

When true, entity data nudges the policy workflow only if no files are saved. Saved files start the workflow through their classification pipeline. Broker callers omit it because their submission trigger owns workflow progress.

Response

End user successfully ingested

end_user_heron_idstring

Changes