Nodes

Nodes are the fundamental building blocks of your workflows in PushFire. Each node represents a specific action, a condition, or a control point within your communication flow.

Think of nodes as puzzle pieces. Each piece has a specific role, and when you connect them in the right order, you create a complete, functional flow that automates your communications.

Nodes are connected together to form a directed graph, where each connection represents the execution flow. This allows you to build simple workflows with a single path or complex workflows with multiple branches and conditions.

Start Nodes

• Start Node: The entry point of your workflow. It defines when and how the flow is triggered. It can be automatic (when a subscriber enters a segment) or manual (triggered directly from your application).

Communication Nodes

These nodes are responsible for actually sending messages to your subscribers:

• Email Notification Node: Sends professional, personalized emails. Supports full HTML, images, and dynamic parameters for personalization.
• Push Notification Node: Sends push notifications to mobile and web devices. Ideal for immediate alerts and time-sensitive reminders.

Flow Control Nodes

These nodes let you add logic and control how your workflow executes:

• Wait Node: Pauses the workflow execution. It can wait for a specific duration (minutes, hours, days) or until a condition based on tags is met.
• Condition Node: Splits the flow into two different paths based on conditions. It evaluates tags or segment membership to route subscribers down different paths.
• Join Node: Merges multiple workflow branches into a single point. Essential when different paths need to converge into a shared action.

End Nodes

• End Node: Marks the end of a workflow branch. You can have multiple End Nodes for different execution paths.

Each node has specific properties that you configure. For example, an Email Notification Node requires a subject, message body, and sender. A Wait Node requires a duration or a wait condition.

When a workflow runs, each node processes its function in order. If the node is a Wait, the workflow pauses until the condition is met. If it’s a Condition, the flow splits and continues down the appropriate branch.

Adding nodes to your workflow is simple and intuitive. When you click the add-node button between two existing nodes or on a connection point, a form opens where you configure the new node.

The best part is that you don’t need to worry about wiring nodes manually. PushFire automatically manages connections to ensure your workflow always remains a valid graph. When you add a node, the system automatically creates the required connections between the previous node, the new node, and the next node in the flow.

This means you can focus on your workflow logic instead of technical connection details. The system guarantees that all nodes are properly connected and that the flow is valid.

Nodes with Multiple Outputs

Some nodes have multiple outputs that are handled automatically. For example, a Condition Node has two outputs: one for when the condition is true and another for when it’s false. When you add a Condition Node, the system automatically creates a Join Node and configures the connections for both branches, ensuring the flow converges correctly.

Keep Your Workflows Simple
While you can build very complex workflows, it’s best to keep them simple and easy to understand. If a workflow becomes too complex, consider splitting it into multiple smaller workflows.

Use Descriptive Labels
Each node has a customizable label. Use clear, descriptive names that explain what the node does. This makes workflows easier to maintain and understand.

Document with Descriptions
Many nodes include description fields. Use them to explain why a node is configured a certain way. This helps your team understand the workflow logic.

Test Before Activating
Always test your workflows before enabling them in production. Use test subscribers to verify everything behaves as expected.

Each node type has its own detailed documentation covering:

• Step-by-step configuration
• Available options
• Common use cases
• Node-specific best practices
• Troubleshooting

Explore the documentation for each node to learn how to use them effectively in your workflows.