CRM GrapeInstall

Summary

Attaches an existing CRM Grape follow-up sequence (looked up by name or ID) to a ticket, so the CRM creates the follow-ups for each step of the sequence.

Inputs

• ID do Ticket (ticketId) (required) — ID of the ticket that will receive the sequence.
• ID do Contato (contactId) — Optional contact ID. If empty, the ticket's own contact is used (an empty string is sent and the CRM resolves it).
• Buscar Sequência Por (sequenceSearchBy) — Choose whether to identify the sequence by Nome (name, default) or ID.
• Nome da Sequência (sequenceName) (required) — Name of a sequence already created under Follow-ups → Sequências. Shown and used when searching by name.
• ID da Sequência (sequenceId) (required) — ID of the sequence. Shown and used when searching by ID.

Output shape

The JSON response from the CRM Grape webhook action assign_sequence, returned as one or more items (arrays are split into separate items), each linked to its input item.

The exact response fields are defined by the CRM and are not visible in the node source. Errors such as an invalid token (401), a missing sequence or ticket (404) or bad data (400) throw a descriptive message. With Continue On Fail enabled, an item with an error field is returned instead.

Examples

Example 1: Start a nurturing sequence when a new ticket is created

ticketId = {{$json.ticket_id}}; Buscar Sequência Por = Nome; sequenceName = 'Boas-vindas'; contactId left empty.

Example 2: Assign a sequence selected dynamically by ID

ticketId from the previous node; Buscar Sequência Por = ID; sequenceId = {{$json.sequenceId}}.

Links

• n8n community nodes installation guide