Actions32
- Mensagem Actions
- Contato Actions
- Ticket Actions
- Tag Actions
- Kanban Actions
- Sequência Actions
- Consulta Actions
Ticket → Buscar Ticket
AI-generatedSummary
Fetches a single CRM Grape ticket by its ID and returns its full data. It sends the get_ticket_info action to the CRM's n8n webhook endpoint.
Inputs
- ticketId (required) — ID of the ticket to fetch. Sent to the CRM as
ticket_id.
Output shape
The CRM's response for the ticket, emitted as one or more n8n items. An array response becomes one item per element, and an object becomes a single item. Each item is paired with its input item.
The exact fields depend on the Grape API, because the node passes the response through unchanged. Errors map to messages for 401 (invalid or inactive token), 403, 400, 404 (ticket not found) and 500. With Continue On Fail enabled, an item that fails returns
{ error: message }instead of stopping the workflow. This operation only reads data. It uses the webhook token and base URL from the grapeApi credentials.
Examples
Example 1: Look up a ticket's current status and assignee after an incoming webhook supplies its ID.
Resource: Ticket; Operation: Buscar Ticket; ID do Ticket: {{ $json.ticket_id }}
Example 2: Let an AI agent fetch ticket details as a tool.
Resource: Ticket; Operation: Buscar Ticket; ID do Ticket set via $fromAI('ticketId', 'ID do ticket', 'string')