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 WhatsApp connections and other related resources such as messages, contacts, tickets, queues, tags, and WhatsApp sessions. Specifically for the WhatsApp resource and the create operation, it allows users to create a new WhatsApp connection by specifying its name, status, and whether it should be the default connection.

Common scenarios where this node is beneficial include automating the management of WhatsApp connections within a customer support or communication platform, enabling workflows that dynamically add or update WhatsApp connections without manual intervention.

Practical example:

  • Automatically create a new WhatsApp connection when onboarding a new client or setting up a new communication channel.
  • Set the connection status and mark it as default if needed, streamlining the configuration process in multi-connection environments.

Properties

Name Meaning
Nome The name of the WhatsApp connection to be created.
Status The status of the WhatsApp connection. Possible values: CONNECTED, DISCONNECTED, QRCODE, OPENING, PAIRING, TIMEOUT.
Padrão Boolean flag indicating if this WhatsApp connection should be set as the default one.

Output

The output is a JSON array containing the response from the Press Ticket® API after creating the WhatsApp connection. This typically includes details about the newly created connection such as its ID, name, status, and default flag.

No binary data output is involved in this operation.

Example output snippet (conceptual):

[
  {
    "id": 123,
    "name": "My WhatsApp Connection",
    "status": "DISCONNECTED",
    "isDefault": false
  }
]

Dependencies

  • Requires an active API key credential for the Press Ticket® API.
  • The node uses the API URL and token from these credentials to authenticate requests.
  • The Press Ticket® API must be accessible from the environment where n8n runs.

Troubleshooting

  • Common issues:

    • Invalid or missing API token: The node will fail to authenticate with the Press Ticket® API.
    • Incorrect property values: For example, providing an invalid status value not listed in the options may cause API errors.
    • Network connectivity problems to the API endpoint.

  • Error messages:

    • Authentication errors usually indicate invalid or expired API tokens; verify and update credentials.
    • Validation errors from the API may indicate missing required fields or invalid data formats; ensure all required properties are correctly filled.
    • Unexpected response format errors could occur if the API changes; check for updates or contact API support.

Links and References

  • Press Ticket® Official Website
  • Documentation for the Press Ticket® API (if available publicly) would provide detailed information on endpoints and data structures.

Discussion