First login

Notifly is a SaaS: there is nothing to deploy or configure on your own server. The whole journey from sign-up to the first notification takes a couple of minutes.

1. Sign up

Create an account in the dashboard on notifly.ru (international version — ainotifly.com) or right from the login screen of the Android app (the Create account button). All you need is an e-mail and a password (at least 8 characters). After signing up you will receive a confirmation e-mail — follow the link in it within 24 hours: you cannot log in until the address is confirmed.

Registration is free: the Free plan includes 1,000 events per day — enough for notifications and your first monitors alike. See Quotas and plans for details.

2. First login and the first-run wizard

After logging in you land in the web dashboard app.notifly.ru: on the left — All messages and the list of channels, below them the Management (channels, devices, API tokens), Monitoring, Integrations and Account sections; in the center — the message feed (empty for now).

While you have no channels or no messages yet, the dashboard opens the first-run wizard (app.notifly.ru/welcome). It walks you to your first event in 60 seconds:

1. Create your first channel — the Create first channel button creates a channel called “My first channel” and shows its app token with a copy button.
2. Send your first event — a ready-made request with your token, in curl, Python, Node.js or Go. Copy it and run it.
3. Watch it arrive — the wizard waits and shows the message as soon as it reaches the server.

Below is the First steps checklist, ticked off automatically: first event received; a receiving device connected (other than this browser); first monitor or heartbeat created. The Skip button closes the wizard — it will not open by itself in this browser again.

3. Where to find the app token manually

The app token (prefix A) is the key a channel uses to authorize sending messages. You can find it at any time:

1. Open the Channels section in the side menu.
2. Pick the channel you need (or create a new one with the Create channel button).
3. The channel row has a token field — click it to reveal and copy the token.

4. Connect a receiver

A message in the dashboard feed is not yet a notification on your phone. For notifications to arrive you need a receiving device:

• Android app — sign in with the same e-mail and password. The app keeps a background connection, so notifications arrive even when the app is closed (unless the system puts it to sleep — see the app’s page).
• A dashboard tab in your browser — click Allow notifications in the side menu and confirm the browser prompt. Notifications are shown only while the tab is open: Notifly has no background Web Push.
• iOS app — still in beta and built from source; notifications arrive only while the app is open.

All connected devices are listed in the Devices section.

5. First message and check

Insert your token and run:

curl -X POST "https://api.notifly.ru/message" \
  -H "X-Notifly-Key: <APP_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"title": "Hello", "message": "First message from Notifly", "priority": 5}'

It worked if:

• the response is a JSON object with the message id (code 200);
• the message appeared in the dashboard feed;
• the device from step 4 showed a system notification.

The first two are there but no notification? Go through Notifications not arriving. All sending parameters are described in Sending messages, examples in other languages — in More examples.

6. Next steps

• Create your first monitor or heartbeat — Notifly will probe your site from the cloud or notice that a cron job has stopped checking in.
• Set up escalation — if a message is not read in time, Notifly forwards it to Telegram, email, SMS, a phone call or a team chat.
• Turn on two-factor authentication — sign in with a code from an authenticator app or by confirming on your phone.
• Browse the ready-made recipes — for sysadmins, developers, websites and personal tasks.