Quick Answer: What are HTTP and Webhook Nodes?

[!NOTE] HTTP and Webhook Action Nodes are the bridge between ConvertUniverse and the rest of the internet. The HTTP Request Node allows you to pull data from any public API, while the Webhook Node sends your workflow results (PDFs, JSON, etc.) to another application’s endpoint for further processing or storage.

Core Capabilities

1. External API Integration

Need to check a customer's balance before generating an invoice? Use the HTTP Request Node to fetch their data from your CRM API. You can dynamically build the URL using https://api.mycrm.com/users/{{input.user_id}}.

2. Deep Webhook Automation

Send your processed files to Zapier, Make, or your own custom backend. The Webhook Node supports sending files as Base64 or as a multipart form upload, integrating with virtually any modern web service.

3. Workflow Chaining

Use an HTTP Request to "kick off" a separate automation pipeline. You can even use it to trigger a Sub-Workflow hosted on another instance of the platform.

Configuration Guide

Field	Description	Best Practice
URL	The target endpoint address.	Use HTTPS for security.
Headers	Auth tokens, Content-Type, etc.	Use `{{secret.api_key}}` for secure key injection.
Body	The data being sent.	Use the JSON editor to build complex payloads.
Auth Type	Basic, Bearer, or None.	Use Bearer tokens for most modern REST APIs.

Best Practices

Response Parsing: The AI Agent Node downstream can help parse messy HTML or non-standard JSON responses returned by older APIs.
Error Handling: Monitor the status code (e.g., 200, 404, 500) in the Execution History to troubleshoot connectivity issues.

[!TIP] Processing incoming requests? Use the Webhook Trigger Node to receive data into your workflow instead of sending it out.