> For the complete documentation index, see [llms.txt](https://docs.nodefy.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nodefy.xyz/our-api-guide/user-info.md).

# User Info

This section explains how to pass information about your app's users to the Nodefy API. This enables Nodefy to send targeted notifications to the right users and personalize the notification experience.

**Important Note:** We refer to the users of **your** application as **"External Users"** to distinguish them from the users who manage Nodefy accounts (internal users).

**Identifying External Users** (Optional)

If you are building notifications for many users, it is good practice to include a unique identifier for each user in the payload of your API requests. This identifier should be a string that you can use to identify the user (e.g., a user ID or email address). Use the field `external_user_id` for this purpose.


---

# 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.nodefy.xyz/our-api-guide/user-info.md?ask=<question>&goal=<endgoal>
```

`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.