Actions32
- Mensagem Actions
- Contato Actions
- Ticket Actions
- Setor Actions
- Tag Actions
- WhatsApp Actions
- Sessão WhatsApp Actions
Overview
This node integrates with the Press Ticket® API to manage contacts and other related resources. Specifically, the "Contato" (Contact) resource with the "Atualizar" (Update) operation allows users to update existing contact information in the Press Ticket system.
Typical use cases include:
- Updating a contact's name, phone number, email, or address.
- Adding or modifying additional custom fields for a contact.
- Keeping contact records up-to-date automatically as part of a workflow.
For example, after collecting updated customer details from a form, this node can be used to synchronize those changes with the Press Ticket contact database.
Properties
| Name | Meaning |
|---|---|
| ID do Contato | The unique identifier of the contact to update. |
| Nome | The new or updated name of the contact. |
| Número | The new or updated phone number of the contact (optional). |
| The new or updated email address of the contact (optional). | |
| Endereço | The new or updated physical address of the contact (optional). |
| Informações Adicionais | Additional custom fields for the contact. Each field has a name and a value (optional). |
Output
The node outputs an array of JSON objects representing the response from the Press Ticket API after updating the contact. This typically includes the updated contact data as returned by the API.
Example output structure (simplified):
{
"id": "123",
"name": "Updated Contact Name",
"number": "+5511999999999",
"email": "contact@example.com",
"address": "Rua Exemplo, 123",
"extraInfo": [
{
"name": "CustomField1",
"value": "Value1"
}
]
}
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Press Ticket API.
- The node uses the Press Ticket API base URL and token configured in the credentials.
- Network access to the Press Ticket API endpoint is necessary.
Troubleshooting
- Missing required fields: Ensure that the "ID do Contato" and "Nome" properties are provided; these are mandatory for updating a contact.
- Invalid contact ID: If the contact ID does not exist, the API will likely return an error. Verify the contact ID before updating.
- API authentication errors: Check that the API token credential is valid and has sufficient permissions.
- Malformed additional info: When providing additional fields, ensure each has both a name and a value; otherwise, the API may reject the request.
- Network issues: Confirm connectivity to the Press Ticket API endpoint.
If the node throws an error, it usually contains the message returned by the API or a descriptive message about what went wrong.
Links and References
- Press Ticket API Documentation (example link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage best practices