CRM GrapeInstall

Summary

Sets the notes text on a CRM Grape ticket by sending a set_ticket_notes action to the CRM's n8n webhook endpoint.

Inputs

• ID do Ticket (ticketId) (required) — ID of the ticket whose notes are to be updated.
• Notas (notes) — Multi-line text for the ticket notes. Defaults to an empty string and is always sent, so leaving it empty sends empty notes. Whether that clears existing notes depends on the CRM, which the source doesn't show.

Output shape

The JSON response from the Grape webhook, emitted as one or more n8n items per input item (arrays are split into separate items) and linked to the input item.

The response body is defined by the CRM and isn't described in the node. Errors are thrown with Portuguese messages: 401 invalid or inactive token, 403 action not allowed, 400 invalid data, 404 not found, 500 server error. With Continue On Fail enabled, the item returns { error: message } instead.

Examples

Example 1: An AI agent or workflow records a summary on a ticket after a conversation.

Resource: Ticket; Operation: Definir Notas; ID do Ticket: {{$json.ticketId}}; Notas: {{$json.summary}}

Example 2: Write a fixed note on a specific ticket.

ID do Ticket: 123; Notas: 'Cliente solicitou retorno amanhã.'

Links

• n8n community nodes installation guide