What is a Trigger?

A Pipeline Trigger or just Trigger is an action which causes a persisted pipeline to be executed.

These triggers are the common ones in PIPEFORCE:

Job​

See Pipeline Jobs for more details.

Triggers a pipeline as a job which must be executed after a certain amount of time.

Message

See Messaging for more details.​

Triggers a pipeline in case a message of interest is on the message queue / bus.

Event

See Events for more details.

Triggers a pipeline in case an internal event of interest has occured. Events are quite similar to messages, except that their origin is always the hub backend.

Common event examples are:

• property.created = A new property has been created in the Property Store.

• property.deleted = A new property has been deleted from the Property Store.

• iam.bruteforce.detected = A potential brute force attack has been detected.

Webhook​

See Webhooks for more details.

Triggers a pipeline in case an external system sends a request to one of the custom webhook endpoints.

API Gateway​

See API Gateway for more details.

Triggers a pipeline in case a HTTP request to an API Gateway endpoint was made which in term is linked to a pipeline.

HTTP POST​

See Pipeline HTTP API for more details..

Triggers a pipeline in case a HTTP POST request to the endpoint /api/v3/pipeline was done.