Crafting your unified customer experience

Mapping your customer journeys

Syncing multi-channel touchpoints

Preparing AI copilots for launch

Optimizing engagement workflows

Lining up handoffs to your team

CHANNELS/

Push notifications,
simplified.

Reach every iOS and Android device through APNs and FCM from one platform. Zixflow handles token management and authentication, respects each user's preferences, and tracks every delivery and tap — in native notifications or custom ones your app renders.

Talk to sales

Triggered For Priya

Trigger

Event

Price Drop

Running

Push Notification

Template: Price Drop Alert

Running

Time Delay

Delay: 1 Day

Running

Push Notification

Template: Last Day Reminder

End

Trusted by 1,000+ Brands Messaging Millions Daily

KUKU FM

Recovered

77.09%

of failed messages effortlessly

Native & custom

Native when it's enough.
Custom when it isn't.

Native uses the OS's own UI. Custom sends structured data your app renders its own way.

Native notifications use the operating system's own UI and features — title, body, image and deep link, with nothing to build. Custom notifications are reusable templates with structured data that your app renders itself, so the design, the buttons and the behaviour are yours.

Native: OS-rendered, with images and deep links out of the box
Custom: reusable templates with structured data, rendered in your UI
Up to two action buttons, each with its own deep link
Sticky notifications for updates that shouldn't be swiped away

9:41100

Friday, 22 August9:41

Native

Rendered by iOS and Android

The system's own notification UI — title, body, image and deep link. Nothing to build.

Custom

Rendered by your app

A reusable template with structured data. Your app draws the UI — trackers, action buttons, sticky updates, whatever you design.

Custom payload

{
  "template_id": "rider_tracker",
  "deeplink_url": "shopnest://orders/48213",
  "action_buttons": [
    { "name": "Track Order", "deeplink": "shopnest://track" },
    { "name": "Call Rider", "deeplink": "shopnest://call" }
  ],
  "sticky": true
}

Features

The full
push checklist.

Push is gated by Apple, Google and a permission prompt. The choice of platform is whether those gates are visible or hidden. We chose visible.

01
APNs and FCM — one integration
Reach iOS through Apple Push Notification service and Android through Firebase Cloud Messaging, from one platform and one send.
02
Automatic token management
Tokens registered on install, refreshed when they change, and switched off the moment they go invalid — no stale-token clean-up jobs.
03
Multi-device profiles
One user, every device. Anonymous devices can receive push before sign-up, and merge into the profile when the user is identified.
04
Native and custom notifications
OS-rendered notifications with images and deep links, or reusable custom templates with structured data your app renders its own way.
05
Action buttons with deep links
Up to two buttons per notification, each opening its own screen in your app — and every tap tracked.
06
Rich media
Images, GIFs and video attached to notifications, downloaded and displayed by the SDK.
07
Preference centre & send windows
Per-category opt-ins your users control, and send windows that keep non-urgent pushes to sensible hours.
08
Delivery and engagement tracking
Delivered, Opened and Action Clicked events for every push — down to which button was tapped and where it led.

Push for iOS and Android,
without the token plumbing.

React Native SDK

import { Platform } from 'react-native';
import messaging from '@react-native-firebase/messaging';
import notifee from '@notifee/react-native';
import { Zixflow } from 'zixflow-reactnative';

export async function initializePush() {
  await notifee.requestPermission();

  if (Platform.OS === 'ios') {
    await messaging().requestPermission();
    if (!messaging().isDeviceRegisteredForRemoteMessages) {
      await messaging().registerDeviceForRemoteMessages();
    }
  }

  const token = await messaging().getToken();
  await Zixflow.registerDeviceToken(token);

  messaging().onTokenRefresh((newToken) =>
    Zixflow.registerDeviceToken(newToken),
  );
}

// After login — links this device to Priya's profile
await Zixflow.identify('[email protected]', {
  email: '[email protected]',
  first_name: 'Priya',
});

Sendflow (with Fallback)

curl --request POST \
  --url https://api-ai.zixflow.com/api/ingest/sendflow/v1/YOUR_FLOW_ID/trigger \
  --header 'x-api-key: YOUR_API_KEY' \
  --header 'x-workspace-id: YOUR_WORKSPACE_ID' \
  --header 'Content-Type: application/json' \
  --data '{
    "variables": {
      "name": "Priya",
      "order_id": "48213",
      "eta": "12 min"
    },
    "recipients": {
      "email": "[email protected]",
      "phone": "+919876543210"
    }
  }'

Read the docs

FAQs

Still Have Questions?
We're Here to Help

Yes — push always travels through Apple and Google. You connect your APNs key and Firebase project to Zixflow once, and authentication with both is handled from then on.

Crafting your unified customer experience

Mapping your customer journeys

Syncing multi-channel touchpoints

Preparing AI copilots for launch

Optimizing engagement workflows

Lining up handoffs to your team

CHANNELS/

Push notifications,
simplified.

Talk to sales

Triggered For Priya

Trigger

Event

Price Drop

Running

Push Notification

Template: Price Drop Alert

Running

Time Delay

Delay: 1 Day

Running

Push Notification

Template: Last Day Reminder

End

Trusted by 1,000+ Brands Messaging Millions Daily

KUKU FM

Recovered

77.09%

of failed messages effortlessly

Native & custom

Native when it's enough.
Custom when it isn't.

Native uses the OS's own UI. Custom sends structured data your app renders its own way.

Native: OS-rendered, with images and deep links out of the box
Custom: reusable templates with structured data, rendered in your UI
Up to two action buttons, each with its own deep link
Sticky notifications for updates that shouldn't be swiped away

9:41100

Friday, 22 August9:41

Native

Rendered by iOS and Android

The system's own notification UI — title, body, image and deep link. Nothing to build.

Custom

Rendered by your app

A reusable template with structured data. Your app draws the UI — trackers, action buttons, sticky updates, whatever you design.

Custom payload

{
  "template_id": "rider_tracker",
  "deeplink_url": "shopnest://orders/48213",
  "action_buttons": [
    { "name": "Track Order", "deeplink": "shopnest://track" },
    { "name": "Call Rider", "deeplink": "shopnest://call" }
  ],
  "sticky": true
}

Features

The full
push checklist.

Push is gated by Apple, Google and a permission prompt. The choice of platform is whether those gates are visible or hidden. We chose visible.

01
APNs and FCM — one integration
Reach iOS through Apple Push Notification service and Android through Firebase Cloud Messaging, from one platform and one send.
02
Automatic token management
Tokens registered on install, refreshed when they change, and switched off the moment they go invalid — no stale-token clean-up jobs.
03
Multi-device profiles
One user, every device. Anonymous devices can receive push before sign-up, and merge into the profile when the user is identified.
04
Native and custom notifications
OS-rendered notifications with images and deep links, or reusable custom templates with structured data your app renders its own way.
05
Action buttons with deep links
Up to two buttons per notification, each opening its own screen in your app — and every tap tracked.
06
Rich media
Images, GIFs and video attached to notifications, downloaded and displayed by the SDK.
07
Preference centre & send windows
Per-category opt-ins your users control, and send windows that keep non-urgent pushes to sensible hours.
08
Delivery and engagement tracking
Delivered, Opened and Action Clicked events for every push — down to which button was tapped and where it led.

Push for iOS and Android,
without the token plumbing.

React Native SDK

import { Platform } from 'react-native';
import messaging from '@react-native-firebase/messaging';
import notifee from '@notifee/react-native';
import { Zixflow } from 'zixflow-reactnative';

export async function initializePush() {
  await notifee.requestPermission();

  if (Platform.OS === 'ios') {
    await messaging().requestPermission();
    if (!messaging().isDeviceRegisteredForRemoteMessages) {
      await messaging().registerDeviceForRemoteMessages();
    }
  }

  const token = await messaging().getToken();
  await Zixflow.registerDeviceToken(token);

  messaging().onTokenRefresh((newToken) =>
    Zixflow.registerDeviceToken(newToken),
  );
}

// After login — links this device to Priya's profile
await Zixflow.identify('[email protected]', {
  email: '[email protected]',
  first_name: 'Priya',
});

Sendflow (with Fallback)

curl --request POST \
  --url https://api-ai.zixflow.com/api/ingest/sendflow/v1/YOUR_FLOW_ID/trigger \
  --header 'x-api-key: YOUR_API_KEY' \
  --header 'x-workspace-id: YOUR_WORKSPACE_ID' \
  --header 'Content-Type: application/json' \
  --data '{
    "variables": {
      "name": "Priya",
      "order_id": "48213",
      "eta": "12 min"
    },
    "recipients": {
      "email": "[email protected]",
      "phone": "+919876543210"
    }
  }'

Read the docs

FAQs

Still Have Questions?
We're Here to Help

Yes — push always travels through Apple and Google. You connect your APNs key and Firebase project to Zixflow once, and authentication with both is handled from then on.

Push notifications,simplified.

Trusted by 1,000+ Brands Messaging Millions Daily

Native when it's enough.Custom when it isn't.

The fullpush checklist.

APNs and FCM — one integration

Automatic token management

Multi-device profiles

Native and custom notifications

Action buttons with deep links

Rich media

Preference centre & send windows

Delivery and engagement tracking

Push for iOS and Android,without the token plumbing.

Still Have Questions?We're Here to Help

Do I need my own APNs and FCM setup?

What's the difference between native and custom notifications?

Do you manage device tokens?

Can one user get push on more than one device?

How do users control what they receive?

What do you track?

What if a push can't reach someone?

Push notifications,simplified.

Trusted by 1,000+ Brands Messaging Millions Daily

Native when it's enough.Custom when it isn't.

The fullpush checklist.

APNs and FCM — one integration

Automatic token management

Multi-device profiles

Native and custom notifications

Action buttons with deep links

Rich media

Preference centre & send windows

Delivery and engagement tracking

Push for iOS and Android,without the token plumbing.

Still Have Questions?We're Here to Help

Do I need my own APNs and FCM setup?

What's the difference between native and custom notifications?

Do you manage device tokens?

Can one user get push on more than one device?

How do users control what they receive?

What do you track?

What if a push can't reach someone?

Push notifications,
simplified.

Native when it's enough.
Custom when it isn't.

The full
push checklist.

Push for iOS and Android,
without the token plumbing.

Still Have Questions?
We're Here to Help

Push notifications,
simplified.

Native when it's enough.
Custom when it isn't.

The full
push checklist.

Push for iOS and Android,
without the token plumbing.

Still Have Questions?
We're Here to Help