OpenRuna
Sign in
← Workflows

address validation

31 nodes · httpRequest, splitOut, wait, filter, webhook

Engine
n8n
Nodes
31
Trigger
scheduled/triggered
Source file
1727_Wait_Splitout_Create_Webhook.json

Workflow flow

IntegrationsHTTPSplit OutWaitFilterWebhookSetIF
100%

Filter

Filter

TRIGGER

Webhook

Webhook

ConfigNode

Set

Wait

Wait

get order data

HTTP

Split Out Order Data

Split Out

Set Address Fields

Set

Filter Out PickUpShops

Filter

check if housenumer is not empty

IF

check if addressline 2 contains number

IF

set value of addressline2 as housenumber

Set

check if addressline 2 contains number and letter

IF

set billbee tag manual check

HTTP

set value of addressline2 as housenumber number+letter

Set

Check Address endereco api

HTTP

check if new address is not empty

IF

Split Out Corrected Address

Split Out

set billbee tag

HTTP

Wait1

Wait

set new delivery address to billbee

HTTP

set billbee success

HTTP

21 steps · flows top to bottom, branches left to right

Browse by integration

httpRequestsplitOutwaitfilterwebhook
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

address validation (31-node n8n automation, httpRequest, splitOut, wait, filter, webhook) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

Built in n8n, "address validation" chains 31 nodes to move data between httpRequest, splitOut, wait, filter, webhook. 31 nodes · httpRequest, splitOut, wait, filter, webhook A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Fork it to add error handling, retries, or a notification step without designing the 31-node flow from scratch.
  • Benchmark it against your current httpRequest integration to spot missing steps or redundant nodes.
  • Study how data moves from httpRequest to splitOut before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the httpRequest stack.

Example output

Imported into n8n, "address validation" exposes 31 configured nodes. Trigger type: scheduled/triggered. Integrations: httpRequest, splitOut, wait, filter, webhook. Set your credentials on the httpRequest node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "address validation" JSON into a plain-English runbook, node by node. It can flag where httpRequest rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for httpRequest, splitOut, wait, filter, webhook. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "address validation" — extract httpRequest IDs and secrets into environment variables without changing the 31-node structure.

Frequently asked questions

How do I import "address validation" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "address validation" use?
It uses: httpRequest, splitOut, wait, filter, webhook. The flow diagram above shows how each service connects across the 31 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own httpRequest and splitOut credentials in n8n after import.
What trigger type does "address validation" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "address validation" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for httpRequest, splitOut, wait, filter, webhook.

Related resources