Application automation and triggers
Linx uses services which triggers events on pre-defined conditions or system events and states. The processes that are associated with an event are created in Linx Application Designer, and are executed on Linx Application Server.
Execute a process at a specified time, day and interval.
RESTful Web Service
Expose your RESTful Web Service methods as events in Linx. Implement custom logic on the request or response of any API endpoint.
Watch a directory for file changes, creations, renaming and deletions. Call a process or run some logic when the service event occurs.
Listens to a queue service (E.g. MSMQ, RabbitMQ or AWS) and trigger an event whenever a message arrives.
SOAP Web Service
Assemble and publish Simple Object Access Protocol (SOAP) web service endpoints to allow external web services to call process flows within a service.
Execute a process periodically at a fixed time, date, or at intervals.
Services contain Events (for example, a DirectoryWatch service has a FileCreated and a FileModified event). A Service Event will trigger off processes when they fire (i.e. when a file is created or modified). A Service can contain functions in itself, or link to any other existing Linx process. Depending on the type of service used, you can forward parameters into the processes, for instance a Web Service Service can receive external values, which can then be forwarded to other Linx processes.