> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/messaging-features/ftp-push-and-imports/send-push-notifications-via-ftp.md).

# Send push notifications via FTP

Send push notifications via FTP without API calls: create a CSV file with one row per recipient, name and upload it, and confirm delivery behavior.

Use this workflow to send push notifications without API calls. Create one CSV row per recipient, upload the file to the FTP directory, and Netmera processes the file to send the notifications.

### Step 1: Prepare FTP access

Confirm that FTP Push is enabled for your application. Obtain the FTP host, port, upload path, and credentials from Netmera or your DevOps team.

If your network uses IP allowlisting, provide Netmera with your public egress IP address.

### Step 2: Create the CSV file

Create a UTF-8 encoded CSV file. Use a semicolon (`;`) as the delimiter.

Add the columns in this exact order:

1. `ExternalID`
2. `Text`
3. `Deeplink`

Each row represents one push notification for one user. Use this format:

```
ExternalID;Text;Deeplink
```

For example:

```
12345;Welcome! Check out what’s new.;https://example.com/welcome
67890;Exclusive offers for you.;https://example.com/offers
```

`ExternalID` identifies the recipient. `Text` is the visible push message. `Deeplink` defines the destination when the recipient selects the notification.

{% hint style="info" %}
Use one push notification per row. Do not use `;` inside the **Text** value. It is interpreted as a new column.
{% endhint %}

### Step 3: Add line breaks when needed

Use `\n` in the **Text** value to display a line break in the push message.

For example:

```
Welcome!\nEnjoy exploring our latest features.
```

The recipient sees:

```
Welcome!
Enjoy exploring our latest features.
```

### Step 4: Name and upload the file

1. Give the file a unique name.
2. Include a timestamp in the filename.
3. Upload the CSV file to the FTP directory provided for your application.

For example, use `push-20260810-0900.csv`. A unique filename prevents a new upload from being confused with a previous file.

### Step 5: Confirm the delivery behavior

Netmera processes the uploaded file and sends the notifications to the listed recipients.

{% hint style="warning" %}
Push notifications sent through FTP include the **Inbox** option by default. If your application uses Inbox, these notifications also appear there.
{% endhint %}

{% file src="/files/AOHsLBtKvez7yUQEGgKN" %}
Importing FTP Push
{% endfile %}


---

# 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://user.netmera.com/netmera-user-guide/messaging-features/ftp-push-and-imports/send-push-notifications-via-ftp.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.