Actions29
- Mensagem Actions
- Ticket Actions
- Contato Actions
- API Oficial Actions
- API Plus Actions
Overview
This node integrates with the WhatMaster API to perform various operations related to WhatsApp messaging, tickets, contacts, and two API variants ("API Oficial" and "API Plus"). Specifically for the Contato (Contact) resource and the Definir CRM (Set CRM) operation, the node allows you to assign or update the CRM system associated with a contact in the WhatMaster platform.
Typical use cases include:
- Synchronizing contact information between your CRM system and WhatMaster.
- Automating updates to contact CRM data based on workflow triggers.
- Managing contact metadata within WhatsApp communication workflows.
For example, you might use this node to set or update the CRM system identifier for a contact after receiving new customer data from another system.
Properties
| Name | Meaning |
|---|---|
| Número do WhatsApp | The WhatsApp number in international format (e.g., 5511999999999). |
| External Key | Optional external key to associate with the request or contact. |
| ID do Contato | The unique identifier of the contact to update. |
| CRM | The name or identifier of the CRM system to assign to the contact. |
Output
The node outputs JSON data representing the response from the WhatMaster API after attempting to set the CRM for the specified contact. The exact structure depends on the API response but generally includes confirmation of the update or error details.
No binary data output is involved in this operation.
Example output JSON snippet (conceptual):
{
"success": true,
"contactId": "12345",
"crm": "Salesforce"
}
If an error occurs, the output will contain an error field with the message.
Dependencies
- Requires configuration of WhatMaster API credentials including:
- A Bearer token for authorization.
- An external code identifier used in the API URL path.
- The node uses the WhatMaster REST API endpoint:
https://back.whatmaster.com.br/v1/api/external/{externalCode} - No additional external services are required beyond the WhatMaster API.
- The node expects valid WhatsApp numbers and contact IDs as input.
Troubleshooting
Missing Credentials:
Error: "No credentials found. Please configure the WhatMaster API credentials."
Solution: Configure the API credentials with a valid Bearer token and external code.Missing Bearer Token or External Code:
Errors indicating these are required mean the credentials are incomplete.
Solution: Ensure both token and external code are set in the credentials.Required Parameters Missing:
For example, if the WhatsApp number or CRM value is empty, the node throws errors like:- "Número do WhatsApp é obrigatório."
- "Mensagem é obrigatória." (for other operations)
Solution: Provide all required parameters according to the operation.
Unsupported Operation or Resource:
If an unsupported resource or operation is selected, the node throws an error indicating so.
Solution: Verify that the resource and operation names are correct and supported.API Request Failures:
Network issues or invalid API responses may cause errors.
Solution: Check network connectivity, API status, and validity of input data.
Links and References
- WhatMaster API Documentation (Assumed URL based on API base URL)
- n8n Documentation on Creating Custom Nodes
- WhatsApp Business API general info: https://www.whatsapp.com/business/api
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.
