Send Mobile Push node

This node allows to communicate automatically with customers by means of mobile push notifications.


  • You must have your own mobile application.
  • You must configure Synerise SDK.

Node configuration

  1. Click the pencil icon on the node.
    Result: A pop-up opens.
  2. From the Template type dropdown list, select the mobile push type.
  3. From the Select push template, select the template of the mobile push.
  4. If you want to make sure that this message is sent to a customer, even it exceeds the global limit of this type of messages for a single customer per day (more information is available here), enable the Ignore limits toggle. You may apply it to system messages such as a transaction confirmation, notifications about order delays, and so on.

  5. If you want to add the custom event parameters with constant values to the automatically generated events in the mobile push channel, in the Additional parameters section, click Define. The full instruction on this section is available at this link.
  6. To

    impose a limit on the action, switch the Action limit toggle. Enter a number and from the dropdown list, select the time unit. You can define how many times this action can be executed for the whole automation process (workflow), or you can define how many times per second/minute/hour/day/week/month can be executed.

  7. If

    If you want to monitor the entries into this step, switch the Track datapoints toggle on. As a result, events related to the movement between nodes (automation.clientPathStep) will be available in the Analytics module to use. These events (automation.clientPathStep, automation.clientEndStep, automation.startPath) are displayed on the activity list on the profile card regardless of the configuration of this option.

  8. Confirm by clicking Apply.

Example of use

Example of use
Example of an automation process that uses the Send Mobile Push action

The purpose of this workflow is to send a mobile push notification with a welcome message informing about access to special offers.

  1. The Profile Data Changed trigger that reacts to birth date changes.
  2. The Profile Filter condition node checks if the birthdate change meets the requirement of a segmentation that defines customers as adults.
  3. If customers belong to the segmentation, they proceed to the next stage. A mobile push is sent to them.
  4. When the push is sent, the workflow ends.

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.



Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker