Martini Triggers

Triggers let you start services and workflows automatically—via API calls, events, schedules, received messages, etc. This flexibility makes it easy to automate business processes, integrate external systems, and respond to real-time events without manual intervention.

Trigger Types

Message Broker Triggers

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

• AWS SQS Listener Trigger
• JMS Trigger
• Kafka Trigger
• Redis Pub/Sub Trigger

Directory Triggers

Start services and workflows when files or directories change:

• Directory Watcher Trigger
• FTP Client Trigger

HTTP Triggers

Start services and workflows on HTTP requests:

• HTTP Filter Trigger
• URL Alias Trigger

Communication Triggers

Start services and workflows on incoming emails or instant messages:

• Email Trigger
• XMPP Trigger

Data Change & Subscription Triggers

Start services and workflows on new data or subscription updates:

• RSS Trigger
• MongoDB Listener Trigger

Scheduled Triggers

Start services and workflows on a schedule:

• Scheduler Trigger

Tracker Resubmit Trigger

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

• Tracker Resubmit Trigger

Using Triggers in Workflows

To learn how to use triggers in workflows, see Martini Workflows Trigger Nodes

Using Triggers in Services

To learn how to use triggers in services, see Invoking Services via a Trigger

Helpful Resources

• Creating Martini Packages
• Workflow Pages - Everything you need to know about workflows
• Martini Workflows Trigger Nodes
• Services Pages - Everything you need to know about services
• Invoking Services via a Trigger
• Community Q&A: Martini Community Have a Question? Post or search it here.