Emvion Venabo icon

Emvion Venabo

Interact with the emvion venabo API

Address → Create

AI-generated

Summary

Create a new address in Venabo.

Inputs

  • name (required) — Name of the address (required)
  • firstName — First name
  • lastName — Last name
  • street — Street
  • zipCode — Zip code
  • city — City
  • countryCode — Country code (default: DE)
  • phone — Phone
  • phoneNumber1 — Phone number 1
  • phoneNumber2 — Phone number 2
  • phoneNumber3 — Phone number 3
  • phoneNumber4 — Phone number 4
  • email — Email address
  • alternativeEmail — Alternative email
  • homepage — Homepage URL
  • reference — Reference
  • customerReference — Customer reference
  • supplierReference — Supplier reference
  • salesLeadReference — Sales lead reference
  • extra — Extra info
  • comment — Comment (textarea)
  • active — Whether the address is active (default: false)
  • receiptBlock — Traveling expenses receipt block (default: false)
  • travelingExpensesType — Traveling expenses type
  • travelingExpensesKm — Traveling expenses km (parsed to float if provided)
  • travelingExpensesFlatPrice — Traveling expenses flat price (parsed to float if provided)
  • dueAmount — Due amount (parsed to float if provided)
  • customFields — Custom fields (key-value pairs, multiple values allowed)
  • requestOptions — Node settings: batching (batchSize, batchInterval), proxy, timeout, allowUnauthorizedCerts

Output shape

The created address record from the Venabo API, including assigned ID and all populated fields.

The node sends a POST request with the provided properties in the request body. Required: name. All other parameters are optional and default to empty string, false, or the specified defaults (e.g., countryCode defaults to DE). Numeric fields (travelingExpensesKm, travelingExpensesFlatPrice, dueAmount) are parsed to parseFloat($value) when non-empty. Custom fields are sent as an object of key-value pairs derived from the fixedCollection input. Request options allow configuring batching, proxy, timeout, and SSL validation.

Links

Discussion