> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/scalars/any.md).

# Any

Arbitrary JSON value scalar type

Audience: Programmer

The `Any` scalar type represents an arbitrary JSON value of any type - object, array, string, number, boolean, or null.

## Format

* Accepts any valid JSON value
* Can be object, array, primitive, or null
* No schema validation
* Serialized as JSON

## Usage

```graphql
type WorkflowSignal {
  id: ID!
  name: String!
  payload: Any  # Can be any JSON value
}

mutation {
  createWorkflowSignal(input: {
    name: "process_order"
    payload: {
      "orderId": "12345",
      "items": [
        {"sku": "ABC", "qty": 2},
        {"sku": "XYZ", "qty": 1}
      ],
      "priority": 1,
      "rush": true
    }
  }) {
    signal {
      id
      payload
    }
  }
}
```

## Valid Values

All of these are valid Any values:

```graphql
# Object
payload: { "key": "value" }

# Array
payload: [1, 2, 3]

# String
payload: "simple string"

# Number
payload: 42.5

# Boolean
payload: true

# Null
payload: null
```

## Use Cases

* Workflow payloads with dynamic structure
* Configuration objects
* Event data with varying schemas
* Integration payloads
* Backwards compatibility

## Best Practices

1. Use sparingly - prefer typed fields when possible
2. Document expected structure
3. Validate on the server side
4. Consider using Map for object-only data
5. Version your payload structures

## Comparison with Map

* **Any**: Accepts any JSON value (objects, arrays, primitives)
* **Map**: Only accepts JSON objects

## See Also

* [Map](/graphql-api/scalars/map.md) - JSON object scalar
* [WorkflowSignal Type](/graphql-api/types/workflowsignal.md) - Uses Any for payloads


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/scalars/any.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.