Space Cloud can be used to create event triggers on database or custom events. The in-built eventing queue in Space Cloud reliably invokes webhooks to carry out any custom logic.
Event triggers enable:
Event triggers are excellent for carrying out asynchronous business logic. Following are a few use cases of event triggers:
You add an event trigger to Space Cloud via Mission Control. Each event trigger has
type, webhook and other configurable parameters.
Events can be of the following types:
CRUD_CREATE: When a row/document gets created.
CRUD_UPDATE: When a row/document gets updated.
CRUD_DELETE: When a row/document gets deleted.
FILE_CREATE: When a file/folder is created.
FILE_DELETE: When a file/folder is deleted.
<CUSTOM>: Whenever you queue a custom event to Space Cloud.
Whenever an event takes place (e.g., insert mutation via Space Cloud or a custom event), Space Cloud invokes the webhook with the event payload. If the webhook responds with a
2xx status code, Space Cloud marks the event to be
processed. Otherwise, it retries the webhook, a certain number of times (configurable) before finally marking it as
Space Cloud stores the events log in
event_logs table in the eventing database (both of them are configurable). The primary database that you selected while creating a project is selected as the eventing database by default.
In some cases, you would want to verify the sender of the request received by your service. This is required when your service is running in an open or untrusted network.
Space cloud adds a
X-SC-Token header which contains a token containing the identity of the caller space cloud instance. This token can be used to check if the incoming request is coming from an authentic source. This token is signed with the
secret key provided in the project’s configuration.