Press Ticket icon

Press Ticket

Interage com a API do Press Ticket®
Join our community

Actions32

Overview

This node integrates with the Press Ticket® API to manage contacts, messages, tickets, queues, tags, WhatsApp connections, and sessions. Specifically for the Contato (Contact) - Criar (Create) operation, it allows users to create a new contact in the Press Ticket system by providing details such as name, phone number, email, address, and additional custom fields.

Typical use cases include:

  • Automating the creation of customer or client contacts from form submissions or CRM systems.
  • Adding new leads or users into the Press Ticket platform for further communication or ticketing.
  • Enriching contact data with extra information fields dynamically.

Example: Automatically creating a contact when a new user signs up on a website, including their name, phone, email, and any custom metadata.

Properties

Name Meaning
Nome The full name of the contact. This is a required field.
Número The phone number of the contact. Optional.
Email The email address of the contact. Optional.
Endereço The physical address of the contact. Optional.
Informações Adicionais Additional custom fields for the contact. Multiple key-value pairs can be added here.

Output

The output JSON contains the response from the Press Ticket API after creating the contact. It typically includes the newly created contact's details such as its unique ID and all submitted properties.

Example output structure (simplified):

{
  "id": 123,
  "name": "John Doe",
  "number": "+5511999999999",
  "email": "john@example.com",
  "address": "Rua Exemplo, 123",
  "extraInfo": [
    { "name": "CustomField1", "value": "Value1" },
    { "name": "CustomField2", "value": "Value2" }
  ]
}

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Press Ticket® API.
  • Needs an API token credential configured in n8n to authenticate requests.
  • The node uses HTTP requests to the API endpoint defined in the credentials.

Troubleshooting

  • Missing Required Fields: If the "Nome" property is not provided, the API will likely reject the request. Ensure all required fields are filled.
  • Invalid API Token or URL: Authentication errors may occur if the API token or base URL is incorrect or expired. Verify credentials configuration.
  • API Response Format Errors: Unexpected API responses or network issues might cause errors. Check network connectivity and API status.
  • Extra Info Format: When adding additional fields, ensure each has both a name and value; otherwise, the API might ignore them or return an error.

Links and References

Discussion