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 unblocks a contact in a messaging or communication platform. It is useful in scenarios where a user has previously blocked a contact and now wants to restore communication by unblocking them. For example, a customer support workflow might use this node to automatically unblock a customer contact after resolving an issue.
Use Case Examples
- Unblocking a contact by specifying their contact ID and session ID to resume communication.
- Automating the unblocking process in a CRM system to ensure contacts are reachable after certain conditions are met.
Properties
| Name | Meaning |
|---|---|
| Session | The session identifier used to authenticate and specify the context for the unblock operation. |
| Contact Id | The unique identifier of the contact to be unblocked. |
| 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 unblock operation was successful.contactId- The ID of the contact that was unblocked.message- Additional information or status message about the unblock operation.
Dependencies
- Requires an API key or session token for authentication to the messaging platform.
Troubleshooting
- Ensure the session ID and contact ID are valid and correctly formatted to avoid errors.
- If the request times out, consider increasing the timeout setting in Request Options.
- If SSL certificate validation fails, enabling 'Ignore SSL Issues' may help but use with caution due to security risks.
- Proxy settings must be correctly configured if used, otherwise requests may fail.