> 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/queries/nodeattachments.md).

# NodeAttachments

nodeAttachments Query

Audience: Programmer

Fetches an attachment object given its ID. This query follows the Relay Global Object Identification Specification and is used to retrieve a single attachment by its unique identifier.

## Arguments

| Name | Type  | Description                                         |
| ---- | ----- | --------------------------------------------------- |
| `id` | `ID!` | The unique identifier of the attachment to retrieve |

## Return Type

`NodeAttachments` - An interface that returns an object implementing the NodeAttachments interface. Currently, this is implemented by the `Attachment` type.

## Usage Example

### GraphQL Query

```graphql
query GetAttachment($id: ID!) {
  nodeAttachments(id: $id) {
    id
    ... on Attachment {
      filename
      contentType
      size
      url
      refId
      reftype
      metadata
      createdAt
      updatedAt
    }
  }
}
```

### Query Variables

```json
{
  "id": "QXR0YWNobWVudDoxMjM="
}
```

### JavaScript Example

```javascript
const getAttachment = async (attachmentId) => {
  const query = `
    query GetAttachment($id: ID!) {
      nodeAttachments(id: $id) {
        id
        ... on Attachment {
          filename
          contentType
          size
          url
          refId
          reftype
          metadata
          createdAt
          updatedAt
        }
      }
    }
  `;

  const response = await fetch('/graphql', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': `Bearer ${accessToken}`
    },
    body: JSON.stringify({
      query,
      variables: { id: attachmentId }
    })
  });

  const { data } = await response.json();
  return data.nodeAttachments;
};
```

## Related

* [Attachment Type](https://github.com/pyck-ai/docs/blob/main/graphql/types/Attachment.md)
* [attachments Query](/graphql-api/queries/attachments.md)
* [createAttachment Mutation](https://github.com/pyck-ai/docs/blob/main/graphql/mutations/createAttachment.md)
* [NodeAttachments Interface](https://github.com/pyck-ai/docs/blob/main/graphql/interfaces/NodeAttachments.md)


---

# 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/queries/nodeattachments.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.