CRM GrapeInstall

Summary

Updates the name and/or email of an existing CRM Grape contact, identified by its contact ID, by sending an update_contact action to the CRM's n8n webhook endpoint.

Inputs

• ID do Contato (contactId) (required) — ID of the contact to update.
• Nome (contactName) — New contact name. Defaults to an empty string.
• Email (contactEmail) — New contact email. Defaults to an empty string.

Output shape

One JSON item per input item, containing the response body returned by the Grape webhook for the update_contact action (typically the result of the update; exact fields are defined by the CRM API).

Name and email are always sent in the payload, even when left empty. The source does not filter out empty values, so an empty field may be sent as an empty string, and whether the backend ignores or overwrites it is not visible here. Errors (401 invalid token, 403 not allowed, 400 invalid data, 404 not found, 500 server error) are thrown with Portuguese messages; with 'Continue on Fail' enabled, an item with an error field is returned instead. Requires Grape API credentials (base URL and webhook token). Usable as an AI agent tool.

Examples

Example 1: Correct a contact's email after a customer provides a new one.

Resource: Contato; Operation: Atualizar Contato; ID do Contato: {{$json.contactId}}; Email: new@example.com; Nome: set to the current name so it isn't blanked.

Example 2: Rename a contact using data from a previous node.

ID do Contato: {{$json.id}}; Nome: {{$json.fullName}}; Email: {{$json.email}}

Links

• n8n community nodes installation guide