Custom Field variables in automations

Two different access paths exist for lead fields in automations, mirroring the Tabellenschema vs. Custom Fields split:

Field type	Variable path
Tabellenschema	{{<trigger>.tableEntry.data.<key>}}
Custom Field	{{<trigger>.tableEntry.customFieldData.<uuid>}}

The variable picker handles this automatically — if you click a Custom Field chip in the variable panel, it inserts the customFieldData.<uuid> path with the right UUID baked in.

Why UUIDs instead of names

Custom Fields have stable UUIDs and editable names. The UUID never changes; the display label can be renamed any time without breaking anything downstream.

If automations referenced Custom Fields by name, a customer renaming “Email” to “E-Mail” would silently break every flow that touches it. By keying on UUID, renames are zero-impact.

The tradeoff: the variable path looks ugly. customFieldData.f3a8c2b1-9e4d-4f1a-... is not a thing a human types correctly. So you don’t. Use the variable picker.

Telling them apart in the variable panel

The variable panel groups outputs by source. Custom Fields are highlighted in green to distinguish them from regular Tabellenschema fields.

Click a chip to copy its path. Paste it into the body field.

Common Custom Field paths

For the canonical fields most pools have:

Field	Type	Likely path
email	Custom Field, type email	{{<trigger>.tableEntry.customFieldData.<email-uuid>}}
phone	Custom Field, type phone	{{<trigger>.tableEntry.customFieldData.<phone-uuid>}}
kurs / Terminwunsch	Custom Field, type dropdown	{{<trigger>.tableEntry.customFieldData.<terminwunsch-uuid>}}

The UUID is specific to the org, not the field type — the email field has a different UUID in every org.

Finding the UUID without using the picker

If you need to write the path manually (Make.com flows or custom HTTP integrations):

1. Open the Custom Field’s config in Settings → Custom Fields.
2. The field’s URL or its edit dialog exposes the UUID.

Alternatively, POST a test lead via the Ingress webhook and inspect the customFieldData object in the response — keys are the UUIDs.

Empty / missing values

If a Custom Field is empty for a particular lead, the variable resolves to an empty string. There’s no special “null” or “undefined” handling — your downstream node has to be tolerant of empty values.

For email subject lines like "Bestätigung für {{firstName}}", an empty firstName renders as "Bestätigung für ". Add a conditional branch or a default-value fallback if that’s not acceptable.

What’s next

You’ve covered the automations group. Move on to Email setup to wire up the actual email-delivery infrastructure that automation “Send email” nodes use.