Lesson 3 of 7

Modules & data mapping

6 min read

Your action module has empty boxes: To, Greeting. Where do they get filled from? From the module before it — if you connect them.

Wiring a value into a slot

A wire says two modules are connected, but it doesn't say which piece of data goes where. That's mapping: you take a field the earlier module produced — a name, an email — and drop it into a slot in the next module. Map the form's email into the To box and the action finally knows who to write to.

Mapping is plumbing: you're connecting one module's output to another module's input, field by field.

Fields become live placeholders

A mapped field isn't a fixed word — it's a placeholder that fills in fresh each run. Map name into a greeting and every run writes that run's name: Hi Anna, then Hi Ben, then Hi Sena. You set it up once with one example; it adapts to every item forever after.

One mapping handles thousands of items — the placeholder pulls the right value for whoever comes through next.

If a mapped field is ever empty for an item — a blank email — the slot fills with nothing. Worth a quick check, or a filter, for the messy real-world cases.