> For the complete documentation index, see [llms.txt](https://docs.onum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/utils/crc32-checksum.md).
# CRC32 checksum
## Description
This operation calculates a 32-bit Cyclic Redundancy Check (CRC) value for a given input. A **cyclic redundancy check (CRC)** is an error-detecting code commonly used in digital networks and storage devices to detect accidental changes to raw data.
The algorithm uses a fixed 32-bit polynomial to calculate a short "fingerprint" of the input data, resulting in a 32-bit (one-byte) checksum. This checksum can detect certain types of errors, like single-bit errors or burst errors up to 32 bits, by recalculating the checksum and comparing it with the original.
***
## Data types
These are the input/output expected data types for this operation:
### Input data
 - Data you want to compute the CRC-32 checksum for.
### Output data
 - CRC-32 values of your input data.
***
## Example
Suppose you want to calculate the CRC-32 of a specific set of data:
1. In your Pipeline, open the required [Action](/the-workspace/pipelines/actions.md) configuration and select the input **Field**.
2. In the **Operation** field, choose **CRC32 Checksum**.
3. Give your **Output field** a name and click **Save**. The operation will calculate the CRC32 codes for the strings in your input field. For example:
```
Input data - "hello 1234"
Output data - "7ED8D648"
```
{% hint style="info" %}
You can try out operations with specific values using the **Input** field above the operation. You can enter the value in the example above and check the result in the **Output** field.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/utils/crc32-checksum.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.