Skip to content

Martini Workflows Start Trigger Node

Overview

The Start Trigger Node is the entry point for every Martini workflow, enabling you to execute workflows manually or automatically through API calls. This node cannot be deleted—every workflow always has a Start Trigger Node, ensuring consistent entry and execution.

Every new workflow includes this node by default, providing immediate testing capabilities and seamless integration with REST and GraphQL APIs.

Note: The Start Trigger Node can only be invoked via API call if the workflow is explicitly configured as an operation of a REST or GraphQL API. Simply having a Start Trigger Node does not expose your workflow to external API calls.

When to Use This

Use this when you need to:

  • Allow your workflow to be executed by REST API or GraphQL endpoints (requires explicit API operation configuration)
  • Enable your workflow to be called from another workflow
  • Test workflow functionality during development without external dependencies (manual execution)

Prerequisites

Start Trigger Node

The Start Trigger Node serves as the entry point for all workflows, automatically included when you create a new workflow to enable immediate execution and testing. It cannot be deleted from the workflow canvas.

Good to Know:
The Start Trigger Node is always present in every workflow, but your workflow is only accessible via API calls if you choose to configure it as an operation of a REST or GraphQL API. This means you have full control over which workflows are available to external systems—unconfigured workflows remain private and cannot be triggered from outside Martini.

Getting Started

To see the Start Trigger Node in a real-world context, follow our Quick Start Guide which demonstrates building a complete workflow that:

  • Is used as a REST API operation handler with a Start Trigger node processing incoming requests
  • Processes incoming data through connected workflow nodes
  • Returns structured responses to API clients

This practical example shows how the Start Trigger Node integrates with other Martini components in real-world scenarios.

For a simple and minimal test:

  1. Create a new workflow
  2. Observe the Start Trigger Node already present on the canvas
  3. Configure the Output of your workflow and add a message string property
  4. Add a Map Node and connect the edge to the Start Trigger Node
  5. Click the arrow on the Map node to open the Map View, look for the message String property and double-click to set the expression
  6. In the Set Expression dialog, type in Hello World, making sure the language field on the lower left is
    set to Plain Text
  7. Click Apply
  8. Save your workflow
  9. Click the Run button to execute your simple workflow
  10. Click the "Output" tab on the Console view to see the "Hello World" message returned by your workflow

Expected result: The workflow executes successfully and returns "Hello World", demonstrating the Start Trigger Node's basic functionality.

Key Terms

To understand Workflow Key Terms and terminologies, see Workflow Concepts

How It Works

The Start Trigger Node operates differently depending on how the workflow is executed:

Manual Execution (Development)

  1. You click the Run button in the Workflow Designer Toolbar
  2. Enter any expected input data and click Run
  3. Execution flows through connected edges to subsequent nodes
  4. Results appear in the Designer console Logs and/or Output tab for immediate feedback

API Execution

  1. An HTTP request hits your configured REST or GraphQL endpoint
  2. Martini routes the request to the associated workflow
  3. The Start Trigger Node accesses the HTTP request data (headers, body, parameters)
  4. The workflow processes the data and returns a response through the endpoint

Important:
The Start Trigger Node will only respond to API calls if the workflow is mapped as an operation of a REST or GraphQL API. Workflows not mapped to an API endpoint cannot be triggered externally, regardless of the presence of the Start Trigger Node.

Edge Connectivity Rules

  • Only nodes connected via edges will execute
  • Disconnected nodes are ignored during workflow execution
  • Multiple paths can branch from the Start Trigger Node

Configuring API Endpoints

The Start Trigger Node enables workflows to function as REST or GraphQL API endpoint handlers.
However, this only occurs if you configure your workflow as an operation of a REST or GraphQL API.

Good to know:
The Start Trigger Node is always present, but your workflows are only accessible via API calls if you intentionally configure them as API operations.
By default, workflows remain private and cannot be triggered externally unless you set up the API mapping yourself.

Configuring REST API Endpoints

To make your workflow accessible through REST API calls, simply link it to a REST API operation.
This lets your workflow handle requests sent to your REST endpoints.

Tip:
For REST APIs, your workflow must have the Start Trigger Node connected to the rest of your workflow nodes. Only nodes linked from the Start Trigger Node will execute when your REST API is called.

To learn more on how to set this up, see
Configuring Services and Workflows for REST API Endpoints.

Configuring GraphQL API Endpoints

When generating a GraphQL server from a schema file or using Martini's GraphQL database reader, you can choose to have Martini automatically generate workflow handlers for your GraphQL operations.
This means your GraphQL queries and mutations will be handled by newly created workflows, each starting with a Start Trigger Node.

Note:
For GraphQL APIs, all generated workflows will already have the Start Trigger Node properly linked to the rest of the workflow, so you can focus on your business logic.

For more details and setup instructions, see
Creating GraphQL APIs.

Troubleshooting

Problem How You'll Know Root Cause Solution
API endpoint returns 404 for workflow containing a Start Trigger HTTP requests fail despite workflow existing Workflow not configured as REST endpoint operation handler Configure REST API endpoint mapping to associate HTTP routes with the workflow

Helpful Resources