Triggers

The TRIGGERS option in the GRAVITY system allows you to register and configure automatic project execution mechanisms for GRAVITY applications. You can define how a project is invoked in response to a specific event or according to a defined schedule.

Within this option, it is possible to assign multiple independent triggers to a single project, each operating according to its own rule. However, it is important to remember that a single trigger can invoke only one project.

The following project invocation mechanisms are available in the TRIGGERS option:

• Time-based schedule – automatic project execution at defined time intervals (e.g., every 10 minutes, daily at 3:00).
• Database notification – execution triggered by a change in the database (e.g., insertion of a new record).
• Web Service – project execution via an external HTTP/REST or SOAP request.
• New file in folder – automatic execution when a file is detected in a monitored directory.
• RabbitMQ message – project execution triggered by a message received from a RabbitMQ message broker.
• TCP connection – project execution triggered by a message received by a TCP server.
• AS2 protocol – project execution triggered by receiving an AS2 message from a partner.

The TRIGGERS option provides full control over when and how GRAVITY projects are executed. This enables support for a wide range of automation and integration scenarios without the need to manually start individual projects.

Creating a Time-Based Trigger

Creating a Database Notification Trigger

Creating a File–Type Trigger

Creating a Webservice Trigger

Creating a RabbitMQ-Type Trigger

If you want more detailed information on how to use the options described above, you can refer to the GRAVITY Process Invocation chapter.

When planning to use automatic triggers, you need to review the Automatic Invocation Server section.