JavaScript where connectors fall short
Drop a JS Code node on the canvas and write JavaScript where connectors fall short — map messy payloads, normalize dates and enums, strip PII, then hand a clean object to the next app step. No sidecar service. No leaving WEXTL.
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Typeform into a JS Code node that maps fields, then Pipedrive and Slack
What Custom Functions (JS) helps you do
JavaScript between the apps you already use
The JS Code node is a first-class step — same ports, same run history as every other node.
- 1
Drop JS Code
Insert it after a webhook, form, or HTTP step — wherever the payload is wrong for the next app.
- 2
Write the transform
Read upstream output, reshape fields in JavaScript, return the object the next node expects.
- 3
Run and inspect
Open run history to see the Function’s inputs and outputs before you schedule or go live.
Map vendor JSON before CRM create
What the JS Code node is for — not a separate microservice, a blue JS Code step on the same canvas as Typeform, CRM, and Slack.
Forms and webhooks rarely match your CRM schema. A JS Code step renames fields, coalesces empty strings, and builds the person payload Pipedrive expects.
Reviewers see the blue JS Code node between Typeform and Pipedrive — not a mystery Lambda in another AWS account.
Typeform into JS Code map step, then Pipedrive and Slack
Normalize HTTP responses before branch
Internal APIs return nested arrays, stringly-typed numbers, and inconsistent nulls. JS Code flattens and types the payload so a Filter step can branch on real fields.
Failed parses show up on that JS Code step in run history — you fix the transform, not grep CloudWatch.
HTTP into JS Code normalize, then Filter to Sheets or Slack
Score and strip PII before send
Before Gmail or an agent auto-sends, JS Code can redact emails/phones and attach a confidence score your policy Filter reads.
Safe path sends; low confidence routes to Slack for human review — the JavaScript guardrail stays on the canvas.
Outlook into JS Code PII/score step, then policy branch to Gmail or Slack