Actions32
- Mensagem Actions
- Contato Actions
- Ticket Actions
- Tag Actions
- Kanban Actions
- Sequência Actions
- Consulta Actions
Contato → Buscar Contato
AI-generatedSummary
Fetches a single CRM Grape contact by ID or phone number via the n8n webhook endpoint (action get_contact_info). The node description says it returns the contact data plus its associated ticket.
Inputs
- Buscar Por (contactSearchBy) — Lookup mode: 'ID' (default) or 'Telefone'. Determines which identifier field is shown and sent.
- ID do Contato (contactId) (required) — Contact ID. Shown and required when searching by ID; sent as contact_id.
- Telefone (phoneNumber) (required) — Phone number with country code, e.g. 5511999999999. Shown and required when searching by phone; sent as phone_number.
Output shape
The JSON response from the Grape API, emitted as one or more n8n items per input item (arrays become multiple items). The description says it contains the contact's data and the associated ticket.
The exact response fields are defined by the Grape server, not by this node. Errors are mapped to messages for 401 (invalid token), 403, 400, 404 (not found) and 500. With 'Continue on Fail' enabled, an item with an {error: message} JSON is returned instead of throwing. Requires grapeApi credentials (base URL and webhook token).
Examples
Example 1: Look up a contact from an incoming WhatsApp message by their phone number.
Resource: Contato; Operation: Buscar Contato; Buscar Por: Telefone; Telefone: {{ $json.from }}
Example 2: Fetch contact details and ticket for a known contact ID from a previous step.
Buscar Por: ID; ID do Contato: {{ $json.contact_id }}