Prerequisites: Your First Workflow or basic Studio familiarity. A test HTTP endpoint (e.g. webhook.site or your own API).
Build an integration workflow: receive a webhook from a SaaS app, map fields with Transform, POST to a notification API, and handle failures.
Goal
When an external system sends {"event": "order.created", "orderId": "123"}, Nodlyn forwards a normalized payload to your API and logs the result.
Step 1 — Webhook trigger
- Add Webhook with path
/ordersand methodPOST. - Copy the webhook URL for your upstream system.
Step 2 — Transform the payload
- Add a Transform node (or Set Fields) after the webhook.
- Map output fields, for example:
source→nodlynexternalId→{{body.orderId}}receivedAt→{{$now}}
Use {{$var.apiUrl}} for the base URL if you store it in Global Variables.
Step 3 — HTTP Request
- Add HTTP Request after Transform.
- Configure:
- URL —
{{$var.apiUrl}}/notificationsor your test endpoint. - Method —
POST. - Body — pass through transformed JSON.
- Headers —
Content-Type: application/jsonplus any API key header.
- URL —
Step 4 — Branch on status
- Add a Condition node checking
{{statusCode}}equals200(or 2xx range). - True branch → Log success.
- False branch → Log error with
{{responseBody}}.
Optional: add Send Email on the false branch for operator alerts.
Step 5 — Test safely
- Run Dry Run with sample webhook body in the test panel.
- Validate, activate, then POST a real payload to the webhook URL.
- Check Jobs → History for the run trace and HTTP response.
Production tips
- Store API keys in global variables or secure credential fields — never hard-code in shared screenshots.
- Use
correlationIdin payloads for idempotent downstream APIs. - For high volume, consider queueing or batch nodes instead of one HTTP call per event.
See also
- Webhook component reference
- HTTP Request
- Transform