Send an event to a particular socket connection.
Before you begin
Section titled “Before you begin”- A Node.js project with Socket.IO configured and connected test clients. Socket-specific operations must run in a socket action.
Direct Message
Section titled “Direct Message”Send an event to a particular socket connection.
Settings
Section titled “Settings”| Setting | Meaning |
|---|---|
| Name | The step identifier used for results in the server action. Sending/joining steps do not return a delivery receipt merely because they have a name. |
| Socket ID | The specific connection identifier to target. It is distinct from the application’s user id. |
| Type | The event/action type selected from the socket definitions. This becomes the emitted eventName, not a primitive data type such as text or number. |
| Input Parameters | Fields generated from the chosen event/action’s $_PARAM definition. Their names and values become the sent parameters. Changing the selected definition clears the earlier parameter mapping; recheck it before testing. |
Verification example
Section titled “Verification example”Obtain the current test client’s Socket ID, then target that ID with a small test event. Confirm the intended connection receives it and another test connection does not.
Context and delivery limits
Section titled “Context and delivery limits”A Socket ID identifies a connection, not an application user or durable inbox. Reconnection can change it. Authorize the recipient association on the server; do not treat a client-supplied socket ID as permission to receive private data.
Connect to page behavior
Section titled “Connect to page behavior”Use client event handlers or the appropriate Server Connect subscription to update the page. Keep authorization, persistence and event delivery as explicit parts of the workflow.
Check your result
Section titled “Check your result”You can choose the intended recipients/context and verify the event or room behavior with test clients.