Skip to main content

Node - Interface Push

Node Function: After clicking an action button, this node can automatically open a new page for the operator or display a pop-up notification. For example, it can open a record detail page or show a warning message.

Push Effects​

1. Notifications​

  • Toast Notification

    • Displays a brief, single-line message at the top of the page.
    • Automatically disappears after a short time.
    • You can configure only the message content and theme color.
    • Can only be pushed to the workflow trigger initiator.

  • Card Notification

    • Displays a notification card at the bottom of the page.
    • Can be configured to remain visible (no auto-dismiss).
    • Supports title, description, and action buttons.
    • Suitable for longer messages or notifications that require user interaction.
    • Card notifications can also be pushed to other users.

2. Open Page Events​

  • Open the record creation page
  • Open the record detail page
  • Open a worksheet view
  • Open a custom page
  • Open a link

Availability Conditions (Can’t See This Node?)​

The Interface Push node is not available in the following types of workflows:

  • Workflows triggered by a date field
  • Scheduled workflows
  • Webhook-triggered workflows
  • Subprocesses

In addition, from the trigger node to the Interface Push node, execution must be instantaneous.

Therefore, the following nodes cannot appear between the trigger node and the Interface Push node, as they may introduce waiting states:

  • Approval node
  • Fill in node
  • Delay node
  • Subprocess / Packaged Business Process (PBP)
  • Loop node

Configuration Examples​

Example 1: When a user submits a ticket record, if customer support determines it is a new requirement, clicking a button automatically creates a requirement record and opens the newly created record.

  1. Add a “Feature Request” button

  2. Configure the workflow associated with this button

  3. Add a “Add Record” node

    This node automatically creates a requirement record.

  4. Add a “Interface Push” node

    Automatically open the newly created requirement record.

    Configuration details:

    • Push Method: Select Open Record Detail Page
    • Record: Specify which record to open. In this case, select the requirement record created by the Add Record node (only nodes before the Interface Push node can be selected).
    • Open Mode:
      • Open in a modal window (popup)
      • Open in a new page (new browser tab)

  5. Publish the workflow and test

Example 2: A simplified version of Example 1: After clicking “Feature Request,” directly create a draft record and open the draft. The record is officially created only after clicking the “Submit” button.

In the Interface Push node configuration, select Open Record Creation Page and enable Create Draft Record.
The record will only be saved after the user clicks Submit.

Example 3: Based on Example 1, adjust the configuration so that after creating the record, it does not automatically open. Instead, display a success message. If the user wants to view the record details, they can click a button in the notification.

In this scenario, use a Card Notification with a button.
Only the configuration of the Interface Push node needs to be adjusted.

Configuration details:

  • Push Method: Select Card Notification

  • Recipients:

    • Can be pushed to the workflow trigger initiator
    • Or to other users (the recipient must be logged in to see the notification)

  • Notification Type: Select Success (green theme)

  • Title and Description:

    • Can be custom text
    • Or dynamically populated using node fields

  • Auto Dismiss: Configure whether the card automatically disappears, based on business needs.

  • Button: Add a button to the card to view the newly created requirement record.

Result:
After clicking “Feature Request,” a notification card appears in the lower-left corner of the page with a button to view the new requirement record.

Scenarios Where Interface Push Will Not Execute​

  • There are Approval, Delay, Fill in, or Loop nodes before the Interface Push node.
  • A button-triggered workflow is converted into a subprocess, and contains a Interface Push node (it will not execute).
  • The pushed link is invalid.
  • Only the first Interface Push node in a workflow will execute. Subsequent Interface Push nodes will not be executed.