HTTP and outbound webhooks
Knot Pro Pack required — The generic outgoing HTTP connector (
action.http) is provided by the Knot Pro Pack extension (private beta, access on request, no public price), not by the free Knot Core. Incoming webhooks (trigger.webhook) stay in Core.
The HTTP connector sends requests to external or internal APIs. Use it alongside Dolibarr when data lives outside the ERP.
🔌 Methods and URL
| Method | Use case |
|---|---|
| GET | Read, health check, fetch resource |
| POST | Create, outbound webhook, JSON payload |
| PUT / PATCH | Idempotent update on remote API |
| DELETE | Remote delete (use with care) |
The URL accepts expressions:
https://api.example.com/v1/orders/{{ nodes.trigger.output.id }}🔌 Headers and authentication
- Add static headers (
Content-Type,Accept, business IDs). - For Bearer or API keys, link an encrypted credential — never paste secrets in the node.
- Knot applies SSRF safeguards documented for admins: local or private URLs may be blocked per server policy.
🔌 Request body
Common templates:
- JSON — most REST APIs.
- Form — legacy compatibility.
- Raw — XML or plain text.
Template JSON with {{ }}:
{ "company": "{{ nodes.dolibarr_tier.output.name }}", "amount": {{ nodes.invoice.output.total_ht }}}🔌 Response and parsing
After the call, the node typically exposes:
- HTTP status code;
- raw body;
- parsed fields (JSON) for downstream edges.
On 4xx/5xx, configure retry on the workflow or a Logic branch to log and alert.
🔌 Idempotency
For POST calls that create remote resources, combine a stable business key with engine idempotency when the partner API allows it, to avoid duplicates after retry.