HTTP Request

The HTTP Request node is the bridge between your internal nLink workflow and the external web. Use it to ping webhooks, download data from external SaaS endpoints, or trigger remote server scripts.

1. Building Your Request

You have granular control over exactly how your network request is dispatched:

• Method & URL: Define standard verbs (GET, POST, PUT, DELETE, PATCH) and dynamically map the URL target via variables.
• Headers & Query Parameters: Inject static standard headers like Content-Type or pass complex URL query strings dynamically from previous workflow steps.
• Request Body: Send raw JSON payloads, simple URL-encoded form data, or even construct heavily complex multipart/form-data payloads complete with binary file uploads directly from the local disk.

2. Authentication Vault Integration

Never hardcode API keys. The HTTP node integrates natively with nLink's secure Credential Vault.

Simply map your node to an existing Basic Auth, Header Auth, OAuth2, or JWT credential type. When the node executes, nLink automatically intercepts the request natively in the backend, injects the highly secure tokens into the headers or query strings, and dispatches it safely.

3. Resiliency & Retries

Network calls fail frequently. The node includes a built-in Auto-Retry engine. If an external API returns a 500 Server Error or a 429 Rate Limit, the node will autonomously pause and re-attempt the request utilizing exponential backoff (e.g., retrying 3 times, waiting 1000ms between attempts) before definitively failing the pipeline.