Node: HTTP Request

The HTTP Request node lets a workflow talk to any external API — your own backend, a Zapier/Make webhook, an ERP, or any service that accepts HTTP calls. It's the general-purpose integration node for anything that doesn't have a dedicated connector in Omnifox.

When to use it

• Push data from a conversation or trigger into an external system (your own CRM, a webhook-fed spreadsheet, etc.).
• Pull data from an external API (pricing, order status) to use in later workflow steps.
• Kick off automations in other tools (Zapier, Make, n8n) from an Omnifox event.

Requirements

• Crece plan or higher (Escala, Exclusivo). On Lite/Conecta the node shows locked with a "Plan+" badge.
• The destination URL, HTTP method, and any auth headers the target service needs.

Configuration

• Method: GET, POST, PUT, PATCH, or DELETE.
• URL (required): supports variables, e.g. https://api.myapp.com/contacts/{{$contact.id}}.
• Headers: key/value table, e.g. Authorization: Bearer {{$secret_token}}.
• Body: text/JSON for POST/PUT/PATCH; supports variables.
• Timeout: in seconds, defaults to 30.

Example

Workflow "Deal won → external CRM": trigger deal.won → HTTP Request node, method POST, URL https://myapp.com/api/deals, header Authorization: Bearer xxx, body {"id":"{{$deal.id}}","email":"{{$contact.email}}"}. success output → "Log Activity"; error output → "Notify the team by email".

Tips

• Content-type defaults to JSON when you don't declare one in the headers.
• GET requests never send a body; a body array there is only kept for legacy integrations as query params.
• Always wire both outputs — a down service shouldn't halt the whole workflow.

Troubleshooting

• Node always routes to the error branch: check that the URL field isn't empty.
• "Plan does not include this node": upgrade to Crece or higher.
• The target service isn't receiving headers: make sure they were entered in the key/value table, not as free text.