Actions101
- 🖥️ Sessions Actions
- 🔑 Auth Actions
- 🖼️ Screenshot Actions
- 📤 Chatting Actions
- 📢 Channels Actions
- 🟢 Status Actions
- 💬 Chats Actions
- 👤 Contacts Actions
- 👥 Groups Actions
- ✅ Presence Actions
- 🏷️ Labels Actions
- 🔍 Observability Actions
✅ Presence → Subscribe
AI-generatedOverview
This node subscribes to presence updates for a specified chat session in a messaging platform. It is useful for monitoring user presence status changes in real-time, such as when a user becomes online or offline in a chat. Practical applications include updating user interfaces with live presence information or triggering workflows based on presence changes.
Use Case Examples
- Subscribe to presence updates for a specific chat session to display online/offline status in a customer support dashboard.
- Monitor presence changes in a team chat to trigger notifications when key members become available.
Properties
| Name | Meaning |
|---|---|
| Session | The name of the chat session to subscribe to presence updates for. |
| Chat Id | The identifier of the chat to monitor presence for. |
| Request Options | Additional options to configure the subscription request, including batching, SSL certificate validation, proxy settings, and request timeout. |
Output
JSON
presenceUpdate- The presence update information received from the subscription, including user presence status and related metadata.
Dependencies
- Requires an API key credential or authentication token to connect to the messaging platform's presence subscription service.
Troubleshooting
- Common issues include invalid session or chat ID causing subscription failures. Verify that the session and chat ID are correct and accessible.
- SSL certificate validation errors may occur if the server uses a self-signed or invalid certificate. Use the 'Ignore SSL Issues' option to bypass this if necessary, but be aware of security risks.
- Timeout errors can happen if the server is slow to respond. Adjust the timeout setting to a higher value if needed.
- Proxy configuration errors may prevent the node from connecting. Ensure proxy settings are correct and credentials are valid if required.