n8n workflows
One authenticated HTTP node for every n8n workflow
Automation workflows are where credentials quietly multiply: every HTTP node holds its own secrets and nothing records what a run actually called. A relay key centralises the outbound path across all of them.
What to expect
- Use the built-in HTTP Request node — method POST, JSON body, bearer credential.
- One credential for every workflow, revocable in the dashboard without editing a single node.
- Blocked and unresolvable targets are refused before a connection is attempted.
- Calls appear in your activity log with target, status and duration for later review.
Working example
n8n
{
"method": "POST",
"url": "https://backfireapi.base44.app/functions/forward",
"authentication": "genericCredentialType",
"sendHeaders": true,
"headerParameters": {
"parameters": [{ "name": "Content-Type", "value": "application/json" }]
},
"sendBody": true,
"specifyBody": "json",
"jsonBody": "{\"url\":\"{{ $json.target }}\",\"method\":\"GET\",\"timeout_ms\":8000}"
}Other environments
Questions about this
Keep reading
Try it with 5,000 free trips.
No card, no subscription, and the balance never expires.