Actions32
- Mensagem Actions
- Contato Actions
- Ticket Actions
- Tag Actions
- Kanban Actions
- Sequência Actions
- Consulta Actions
Ticket → Definir Prioridade
AI-generatedSummary
Changes the priority of an existing CRM Grape ticket by sending a set_ticket_priority action to the CRM's n8n webhook endpoint.
Inputs
- ID do Ticket (ticketId) (required) — ID of the ticket whose priority will be changed. Sent as
ticket_id. - Prioridade (priority) — New priority: Baixa (low), Média (medium), Alta (high) or Urgente (urgent). Defaults to medium, so it is applied even if you leave it untouched.
Output shape
One or more JSON items containing the CRM's webhook response, linked to the originating input item. If the response is an array, each element becomes its own item.
The response body is not defined in the node, so its exact fields depend on the Grape CRM API. Requests use the credential's base URL and webhook token. HTTP errors (401 invalid token, 403 not allowed, 400 invalid data, 404 not found, 500 server error) throw readable Portuguese messages. With Continue On Fail enabled, an item
{ error: message }is returned instead. The node runs once per input item.
Examples
Example 1: Escalate a ticket to urgent when an incoming message contains a keyword.
Resource: Ticket; Operation: Definir Prioridade; ID do Ticket: {{ $json.ticketId }}; Prioridade: Urgente.
Example 2: Lower the priority of a ticket after the issue is resolved.
Resource: Ticket; Operation: Definir Prioridade; ID do Ticket set from a previous node; Prioridade: Baixa.