Creating a timer that sends messages to WebSocket connections
Create a timer, i.e., a trigger to send messages to WebSocket connections on schedule.
Getting started
To create a trigger, you need:
-
API gateway. Messages will be sent to WebSocket connections connected to the API gateway. If you do not have an API gateway, create one.
-
Service account with the
api-gateway.websocketBroadcasterrole. If you do not have a service account, create one.
Creating a trigger
Note
The trigger is initiated within 5 minutes of being created.
-
In the management console, select the folder where you want to create a trigger.
-
Open API Gateway.
-
In the left-hand panel, select Triggers.
-
Click Create trigger.
-
Under Basic settings:
- Enter a name and description for the trigger.
- In the Type field, select
Timer. - In the Launched resource field, select
API gateway.
-
Under Timer settings:
- In the Cron expression field, specify a schedule for sending messages to WebSocket connections as a cron expression.
- Optionally, in the Payload field, specify the message that will be sent to WebSocket connections if the timer fires in the
payloadfield. The data type is a string up to 4,096 characters long.
-
Under API gateway settings:
- In the API gateway field, select the API gateway.
- In the Path field, specify the path in the OpenAPI specification. Messages will be sent through WebSocket connections established using this path.
- In the Service account field, select the service account to send messages to WebSocket connections.
-
Click Create trigger.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.
To create a trigger that sends messages to WebSocket connections, run this command:
yc serverless trigger create timer \
--name <timer_name> \
--cron-expression '<cron_expression>' \
--payload <message> \
--gateway-id <API_gateway_ID> \
--gateway-websocket-broadcast-path <path> \
--gateway-websocket-broadcast-service-account-id <service_account_ID>
Where:
--name: Timer name.--cron-expression: Schedule for sending messages to WebSocket connections as a cron expression.--payload: Message that will be sent to WebSocket connections if the timer fires. The string length must not exceed 4,096 characters.
--gateway-id: API gateway ID.--gateway-websocket-broadcast-path: Path in the OpenAPI specification. Messages will be sent through WebSocket connections established using this path.--gateway-websocket-broadcast-account-id: Service account ID with permissions to send messages to WebSocket connections.
Result:
id: a1s5msktijh2********
folder_id: b1gmit33hgh2********
created_at: "2023-08-04T15:19:15.353909857Z"
name: timer
rule:
timer:
cron_expression: 5 10 ? * * *
payload: <message>
gateway_websocket_broadcast:
gateway_id: d4eofc7n0mh2********
path: /
service_account_id: aje3932acdh2********
status: ACTIVE
To create a timer, use the create REST API method for the Trigger resource or the TriggerService/Create gRPC API call.
Checking the result
Check that the trigger operates correctly. Do it by viewing the API gateway logs that present information about its incoming requests.