Actions101
- š¤ Chatting Actions
- š„ļø Sessions Actions
- š Auth Actions
- š¼ļø Screenshot Actions
- š¢ Channels Actions
- š¢ Status Actions
- š¬ Chats Actions
- š¤ Contacts Actions
- š„ Groups Actions
- ā Presence Actions
- š·ļø Labels Actions
- š Observability Actions
Overview
This node operation blocks a contact in a messaging or communication platform. It is useful for scenarios where you want to prevent a specific contact from sending messages or interacting with you. For example, you might use this node to block spam contacts or unwanted users automatically based on certain triggers.
Use Case Examples
- Automatically block a contact when they send a spam message.
- Block a contact based on user input or external criteria.
Properties
| Name | Meaning |
|---|---|
| Session | The session identifier used to authenticate and specify the user session for the blocking operation. |
| Contact Id | The unique identifier of the contact to be blocked. |
| Request Options | Additional options to control the request behavior such as batching, SSL certificate validation, proxy settings, and timeout. |
Output
JSON
success- Indicates whether the contact was successfully blocked.contactId- The identifier of the contact that was blocked.message- Additional information or status message about the block operation.
Dependencies
- Requires an API key or session token to authenticate the request to the messaging platform's backend service.
Troubleshooting
- Ensure the session token is valid and has not expired to avoid authentication errors.
- Verify the contact ID is correct and exists in the system to prevent errors related to invalid contacts.
- If SSL issues occur, consider enabling the 'Ignore SSL Issues' option, but be aware of the security implications.
- Check proxy settings if requests fail to reach the server, especially in corporate or restricted network environments.
- Adjust timeout settings if the server response is slow to avoid premature request abortion.