What is Customer.io webhooks?
Customer.io sends several kinds of outbound webhooks. A workflow's Send and receive data action can call an external API for each person moving through an automation. Reporting webhooks send message delivery activity to a configured endpoint. The Data Pipelines webhook destination forwards selected source data after applying its mapping.
Workflow and reporting webhooks use X-CIO-Timestamp and X-CIO-Signature. Customer.io signs the raw bytes formed by the literal v0:, the timestamp, another colon, and the untouched body with HMAC SHA-256. Reporting webhook keys are configured with the reporting endpoint, while workflow signing keys are stored under the workspace's API and webhook credentials.
The Data Pipelines destination has a different optional scheme. When a shared secret is set, it sends X-Signature, a hex-encoded HMAC SHA-1 digest of the request body. Receivers must not apply the X-CIO-Signature algorithm to this header. Delivery timing also differs: workflow actions have a 16-second timeout and retry selected failures up to 11 times over about an hour, while reporting webhooks use a four-second timeout and can retry over seven days.
These callbacks carry customer, campaign, or delivery data to an endpoint selected by the workspace. They do not crawl the endpoint's pages or affect AI search and model training. Robots.txt has no place in any of the Customer.io webhook flows.
