Minting Links in Automations

Portal links are created by the portal.link.mint node (label: Portal-Link erstellen), an action node in the automations editor. It creates a personal portal link for one lead and exposes the URL to downstream nodes.

Fields

Field	Description
`tableEntryId`	The lead the link is created for. Almost always a variable from the trigger, e.g. `{{<triggerNodeId>.tableEntry.id}}` (the variable picker inserts this)
`portalScope`	The scope editor described below

Scope editor

Section	Semantics
Funktionen	What the link can do — currently booking; reschedule/cancel/detail-edit are shown but not yet available
Standorte	`Alle Standorte` or an explicit selection. The wildcard is applied per run, so locations created later are covered by future links
Terminarten	`Alle Terminarten` or a narrowed selection. A link only ever offers what is actually bookable at the selected locations
Buchungsfenster	Optional horizon/notice overrides; leave empty to use the org defaults from the portal settings

Which calendars serve which appointment type is never configured on the node — the platform resolves it from its bookability data when the step runs. See What a link offers.

Output

Variable	Content
`{{<nodeId>.portalUrl}}`	The full personal link, e.g. `https://portal.rocketlead.io/3f9a…`

Use it in any downstream send node — an email body, a seven.whatsapp.send template parameter, or a webhook payload.

Failure behavior

The guarantee: a dead link is never delivered. If the link cannot be created for a reason that won’t fix itself — the lead was deleted, a selected location no longer exists, or nothing is bookable for the selection — the run fails permanently before any send node executes. The failed run and its reason appear in the automation’s run overview.

Two details worth knowing:

Under the Alle Standorte wildcard, a location with nothing bookable is simply left out of the link; the run only fails if that leaves nothing at all. An explicitly selected location with nothing bookable fails the run — an explicit pick that offers nothing is treated as a configuration mistake, not silently dropped.
Transient infrastructure errors retry normally, and a retried step re-sends the same link — duplicate deliveries never contain two different links.

Example flow

table.entry.added  (new lead)
        │
portal.link.mint  (book · alle Standorte)
        │
seven.whatsapp.send  (template param: {{<mintNodeId>.portalUrl}})

When the lead books, calendar.appointment.booked fires on the same lead entry — confirmation and reminder automations chain on normally.