Actions104
- Ticket Actions
- Setor Actions
- Tag Actions
- WhatsApp Actions
- Sessão WhatsApp Actions
- Presença Actions
- Grupos WhatsApp Actions
- Listar Grupos
- Criar Grupo
- Obter Grupo
- Alterar Nome
- Alterar Descrição
- Adicionar Participantes
- Remover Participantes
- Promover a Admin
- Rebaixar Admin
- Listar Participantes
- Obter Link de Convite
- Revogar Link de Convite
- Config. Modo Adicionar Membros
- Config. Modo Anúncio
- Config. Restrição
- Alterar Foto
- Remover Foto
- Listar Solicitações de Entrada
- Aprovar Entrada
- Rejeitar Entrada
- Sair do Grupo
- Usuário Actions
- Resposta Rápida Actions
- Status do Cliente Actions
- Backup Actions
- Configuração Actions
- Log de Atividade Actions
- Log de Erro Actions
- Atualização do Sistema Actions
- Vídeo Actions
- Sistema Actions
Presença → Gravando
AI-generatedOverview
This node interacts with the Press Ticket® API to manage presence indicators in a ticketing system, specifically sending a recording (audio recording) presence indicator for a given ticket. It is useful in scenarios where you want to show that an audio recording is in progress within a ticket conversation, enhancing real-time communication feedback.
Use Case Examples
- In a customer support chat, when an agent starts recording an audio message, this node can send a 'recording' presence indicator to notify the customer that the agent is recording.
- In a collaborative ticketing environment, this node can be used to signal to other agents or users that an audio recording is being made on a specific ticket.
Properties
| Name | Meaning |
|---|---|
| ID do Ticket | The unique identifier of the ticket for which the recording presence indicator will be sent. |
| Duração (ms) | The duration in milliseconds for which the recording indicator should be active. |
Output
JSON
success- Indicates if the presence recording indicator was successfully sent.ticketId- The ID of the ticket for which the presence indicator was sent.duration- The duration in milliseconds for which the recording indicator was active.
Dependencies
- Press Ticket® API with an API token credential
Troubleshooting
- Ensure the provided ticket ID is valid and exists in the system to avoid errors.
- Verify that the API token credential is correctly configured and has the necessary permissions to send presence indicators.
- If the duration is not provided, the node uses a default of 3000 milliseconds; ensure this value is appropriate for your use case.