EvoGo+ icon

EvoGo+

EvoGo Node - integrate EvoGo in your n8n workflows

Actions75

Instance → Fetch Instance

AI-generated

Summary

Fetches a single EvoGo instance by its Instance ID, authenticating with the global admin API key. The source pack only shows the class declaration, so the exact endpoint and response shape are not confirmed.

Inputs

  • adminApiKey (required) — Global administrative API key, sent as the apikey request header.
  • instanceId — ID of the instance to fetch. The field is optional in the UI, but its description says it is required for Fetch.
  • requestOptions — Optional request settings: batching (items per batch, batch interval in ms), ignore SSL issues, HTTP proxy URL, and timeout in ms (default 10000).

Output shape

Presumably a single record describing the requested instance, returned as n8n output items.

The source pack contains only the class declaration, so the response fields and the endpoint used could not be verified. Behavior is inferred from the declared properties, which use declarative routing with an apikey header.

Examples

Example 1: Look up the details of a specific WhatsApp instance before sending messages.

Resource: Instance, Operation: Fetch Instance, Admin API Key set to your global key, Instance ID set to the target instance's ID.

Example 2: Query an instance behind a self-signed certificate on a slow server.

Provide the admin API key and Instance ID. Under Request Options, enable Ignore SSL Issues and raise Timeout to 30000.

Links

Discussion