Actions76
- Message Actions
- Chat Actions
- Contact Actions
- Group Actions
- Create
- List
- Get
- Delete
- Join
- Get Join Info
- Leave
- Get Picture
- Set Picture
- Delete Picture
- Update Subject
- Update Description
- Get Security Info Admin Only
- Set Security Info Admin Only
- Get Security Messages Admin Only
- Set Security Messages Admin Only
- Get Participants
- Add Participant
- Remove Participant
- Promote Admin
- Demote Admin
- Status Actions
- Channel Actions
- Poll Actions
- Profile Actions
- LID Actions
- File Actions
Overview
This node enables interaction with WhatsApp contacts through the Wappfy API, specifically allowing you to block a contact. Blocking a contact prevents them from sending messages or interacting with your WhatsApp account.
Common scenarios where this node is beneficial include:
- Automatically blocking spam or unwanted contacts based on certain triggers.
- Managing contact permissions in bulk workflows.
- Integrating WhatsApp contact management into broader automation processes.
For example, you could use this node to block a contact after detecting suspicious activity or receiving unwanted messages, helping maintain a clean and secure communication channel.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier or phone number of the contact to block |
Output
The node outputs JSON data representing the response from the Wappfy API after attempting to block the specified contact. This typically includes confirmation of the block action or details about any errors encountered.
No binary data output is involved in this operation.
Dependencies
Requires an active Wappfy API credential configured in n8n, including:
- Base URL of the Wappfy API instance.
- Instance name identifier.
- An API key for authentication.
The node makes HTTP POST requests to the endpoint
/api/contacts/blockwith the contact ID and session information.
Troubleshooting
Common issues:
- Invalid or missing Contact ID: Ensure the Contact ID or phone number is correctly provided.
- Authentication failures: Verify that the API key and instance name are correctly set in credentials.
- Network or API endpoint errors: Check connectivity to the Wappfy API base URL.
Error messages:
- Errors returned by the API will be included in the node's output JSON under an error field if "Continue On Fail" is enabled.
- If not continuing on fail, the node will throw an error with the message from the API or request failure.
Resolution tips:
- Double-check input parameters for correctness.
- Confirm API credentials and permissions.
- Review API documentation for rate limits or restrictions.
Links and References
- Wappfy API Documentation (general reference for API endpoints)
- WhatsApp Blocking Best Practices (for understanding blocking behavior)
This summary focuses on the "Contact" resource with the "Block" operation as requested.