Press TicketInstall

Overview

This node integrates with the Press Ticket® API to manage contacts and other related resources. Specifically, for the Contato (Contact) resource with the Obter (Get) operation, it retrieves detailed information about a specific contact by its ID.

Common scenarios where this node is beneficial include:

• Fetching contact details to enrich workflows with up-to-date customer information.
• Integrating contact data retrieval into automated support or communication pipelines.
• Using contact information to trigger further actions such as ticket creation or messaging.

Practical example:

• A workflow that receives a contact ID from an external system and uses this node to fetch full contact details before sending a personalized message or creating a support ticket.

Properties

Output

The node outputs a JSON object representing the contact details retrieved from the Press Ticket® API. The structure corresponds to the API's contact representation, typically including fields such as name, number, email, address, extra information, tags, and other relevant contact attributes.

Example output JSON snippet (simplified):

{
  "id": "123",
  "name": "John Doe",
  "number": "+5511999999999",
  "email": "john.doe@example.com",
  "address": "Rua Exemplo, 123",
  "extraInfo": [
    {
      "name": "Company",
      "value": "Example Ltda"
    }
  ],
  "tags": [
    {
      "id": 1,
      "name": "VIP"
    }
  ]
}

No binary data output is produced by this operation.

Dependencies

• Requires an active connection to the Press Ticket® API.
• Needs an API authentication token credential configured in n8n to authorize requests.
• The node uses the base API URL and token from the configured credentials.

Troubleshooting

• Invalid Contact ID: If the provided contact ID does not exist or is malformed, the API may return an error or empty response. Verify the contact ID is correct.
• Authentication Errors: Ensure the API token credential is valid and has sufficient permissions.
• API Response Format Issues: Unexpected response formats may cause errors; ensure the API version matches the node expectations.
• Network Issues: Connectivity problems to the Press Ticket® API endpoint will cause request failures.

Common error messages:

• "Formato de resposta inválido ao obter contato" (Invalid response format when getting contact): Indicates the API response was not as expected; check API availability and credentials.
• HTTP 401 Unauthorized: Check API token validity.
• HTTP 404 Not Found: Contact ID does not exist.

Links and References

• Press Ticket® API Documentation (example link, replace with actual)
• n8n Documentation on Creating Custom Nodes
• General REST API best practices for troubleshooting connectivity and authentication issues