Skip to content

Workflow Trigger Nodes

Overview

Workflow Trigger Nodes are the entry points for any Martini workflow. These nodes let you start workflows automatically or manually—via API calls, events, schedules, or direct user action. This flexibility makes it easy to automate business processes, integrate external systems, and respond to real-time events without manual intervention.

When to Use This

Use this when you need to:

  • Start a workflow automatically in response to events, schedules, or incoming messages
  • Enable manual or API-based workflow execution
  • Integrate external systems or services to trigger Martini workflows

Prerequisites

Adding a Trigger Node to a Workflow

Getting Started

  1. Open your Workflow from your Martini Package in the Navigator on the left side
  2. Access the Node Library: In the Workflow Designer, click the + icon in the top left panel
  3. Select Your Trigger: Look for nodes ending with "Trigger" in the list
  4. Add to Canvas: Drag your desired Trigger node onto the Workflow Designer canvas

  5. Connect the Flow: Connect your Trigger node's edge to the next node in your workflow

    Critical: The workflow will not execute unless properly connected

Expected Result: You should see your trigger node connected with a line to the next node

Note: You can add multiple Trigger Nodes to a workflow for different invocation methods. Each must be connected to other nodes in the workflow.

Trigger Node Types

Martini supports several trigger node types, each designed for specific use cases.

You can visit each trigger's documentation page to understand its usage and configuration in more detail.

Start Trigger Node

The Start Trigger Node lets you start any Martini workflow manually or via API:

Message Broker Triggers

Start workflows when a message arrives from a broker or queue:

Directory Triggers

Start workflows when files or directories change:

HTTP Triggers

Start workflows on HTTP requests or webhooks:

Communication Triggers

Start workflows on incoming emails or instant messages:

Data Change & Subscription Triggers

Start workflows on new data or subscription updates:

Scheduled Triggers

Start workflows on a schedule:

Tracker Resubmit Trigger

Starts workflows to retry failed transactions or address errors by resubmitting Tracker documents based on their type and state.

Configuring Your Trigger Node

Getting Started

To configure a Trigger node:

  1. Click the arrow on a Trigger node to open its configuration window.
  2. If available, in the Configuration tab, set up the trigger (each type has unique settings).
  3. If available, in the Properties tab, select which properties from the incoming event/message you want to expose to your workflow.

Note: Not all trigger types have both tabs: - Start Trigger Node has neither Configuration nor Properties tabs (requires no setup) - Webhook Trigger has only a Configuration tab (no Properties tab available) - Most other trigger types have both Configuration and Properties tabs

Exposed properties become available to any nodes connected to the trigger node. For example, you can use these in Map nodes or Script nodes. See Accessing and Using Trigger Properties

Expected Result: The workflow is now set up to start when the trigger condition is met.

Troubleshooting

Problem Detection Cause Fix
Cannot save trigger configuration Error message when saving Required field missing Fill in all required fields
Properties not available in workflow Properties missing in Map/Script node Properties not selected in Properties tab or trigger doesn't expose properties Select properties in Properties tab (if available for your trigger type)
Trigger does not activate Workflow does not start Trigger not mapped or misconfigured Check mapping and configuration
Trigger node not working as intended Workflow doesn't start or behaves unexpectedly Invalid value in one or more fields Double-check all configuration values and field entries
Missing Configuration/Properties tab Tab not visible in trigger configuration Trigger type doesn't support that tab This is normal - use only the available tabs for your trigger type
No tabs visible in trigger configuration No Configuration or Properties tabs shown Using Start Trigger Node This is normal - Start Trigger Node requires no configuration

Accessing and Using Trigger Properties

After adding a Trigger Node with a Properties tab:

  1. Click the arrow on the Trigger node to open its configuration window. Open the Properties tab (if available).
  2. Select the checkboxes for the properties you want to expose to your workflow.
  3. The selected properties will become available to the other workflow nodes that are connected to the trigger nodes.
  4. Use these properties in any connected workflow node. For example, use them in a Map node to map them to other workflow properties, or in a Script node to use them directly in code.

Tip: If you do not select a property, it will not be available in your workflow. Some trigger types (like Start Trigger Node and Webhook Trigger) do not expose properties.

Example: Mapping a Property

  • Map body String property from Email Trigger Node Properties to a workflow property called emailMessageBody.

Example: Using a Property in a Script Node

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
// Purchase Order Approval Script Node in a Workflow
// Trigger: Email with "PO-" in subject line
if (subject != null && subject.contains('PO-')) {
    println "Processing purchase order from: ${from}"

    // Parse order details from email body
    def orderAmount = extractOrderAmount(body)

    // Route based on order amount
    if (orderAmount > 10000) {
        approver = "senior-manager"
        println "High-value PO - routing to senior manager"
    } else {
        approver = "department-manager"
        println "Standard PO - routing to department manager"
    }

    // Check for attachments (PO documents)
    hasDocuments = (attachments != null && attachments.size() > 0)
}
Expected Result: You can use property values from objects received by the Trigger Node in your workflow logic (for triggers that expose properties).

How It Works

When a trigger event occurs (e.g., a message arrives, a file changes, or a schedule is met), Martini executes the workflow starting from the Trigger Node. For triggers that support it, selected properties from the event/message are exposed as workflow variables, which you can use in Map or Script nodes for further processing, transformation, or conditional logic. If a property is not selected in the Properties tab, it will not be available in the workflow.

Why It Matters

Trigger nodes make workflows responsive and automated. By connecting external systems, schedules, or events to Martini workflows, you can automate business processes, reduce manual effort, and ensure timely responses to important events.

Troubleshooting

Problem Detection Cause Fix
Property not available in workflow Property missing from Map or Script node Property not selected in Properties tab or trigger doesn't expose properties Select the property in the Properties tab (if your trigger type supports properties)

Helpful Resources