Skip to main content
Newly v2, at app.newly.app and in Newly for Mac, has two services built in: Newly Backend and AI models. For other services, the agent adds them to your app’s code with your own account for that service. There are no one-click connect buttons.

​
What works today

​
Push notifications with OneSignal

Newly v2 doesn’t create a OneSignal account or app for you. You bring your own, and the agent adds OneSignal to your app.

​
What you need

  • A OneSignal account and app, and its App ID.
  • An Apple Push Notifications key (a .p8 file) from your Apple Developer account, added to your OneSignal app. iPhones need it to receive pushes.
  • A Firebase service account file (JSON) added to your OneSignal app, for Android.
Without the Apple key and the Firebase file, notifications fail without showing an error. If pushes never arrive, check these first.

​
Set it up

1

Create your OneSignal app

Sign up at OneSignal, create an app and add your Apple and Firebase credentials there.
2

Ask the agent to add push notifications

Describe when your app should send them. For example: “Send a push notification when someone replies to your post. My OneSignal App ID is …”The App ID isn’t secret, so you can put it in the chat. If sending needs the OneSignal REST API key, don’t paste it into the chat. The agent keeps that key on your backend. You set it yourself as a dev secret with the newly CLI, and contact support for production. See Production and secrets.
3

Test on a real iPhone

Install a TestFlight build of your app on your iPhone, allow notifications when asked, then trigger a notification. Only an organization owner or admin can publish to TestFlight.

​
In-app purchases and payments

There’s no built-in payments connection in Newly v2. Newly doesn’t connect RevenueCat for you, and it doesn’t create products, entitlements or paywalls automatically. To add payments, tell the agent what you want to charge for, such as a monthly subscription that unlocks extra features. The agent asks what it needs and builds it into your app’s code, using accounts you set up with the services involved. Keep these in mind:
  • Apple’s rules: apps on the App Store generally have to use Apple’s in-app purchase for digital goods and features. See From TestFlight to the App Store.
  • Screen order: when your app has sign-in, onboarding and a paywall, the agent keeps them in the order sign-in, onboarding, paywall, home. See Sign-in for your app.
  • Keys: keep private payment keys on your backend, never in the app.

​
Other services

For other services, such as a weather API or a maps provider, ask the agent to add them. If the service needs a private API key, follow these steps.
  1. Get the key from the service.
  2. Set it as a secret on your backend’s api service. You can set dev secrets with the newly CLI. For production secrets, contact support. See Production and secrets.
  3. Ask the agent to call the service from your backend, not from the app.

​
Newly v1 integrations

The Newly v1 (legacy) integrations, such as the RevenueCat and OneSignal connect buttons and Supabase, don’t exist in Newly v2. If you still use Newly v1, see the Newly v1 (legacy) docs.

Data, accounts and Newly Backend

What’s built into Newly Backend.

Ship your iOS app to TestFlight

Test push notifications and purchases on a real iPhone.