Flow Builder

Account Variables

These variables are available in all flows and email templates. Flow-level and node-level values override these.

Flow Auto-Assignment

Automatically assign confirmation and reminder flows to new events based on their market unit. Runs during each cron cycle and can be triggered manually.

No market units found yet — load events first.

Market Unit Timezones

Maps each market unit to its local timezone. Used to calculate “before event” delays and resolve {{event_date}} correctly. New market units are auto-discovered from Airtable events.

No market units found yet — load events first.

Booking Variables

These variables are auto-populated from each Airtable booking + linked event when a flow runs. Use them as {{name}} in SendGrid templates, SMS message text, or as the source field for value mappings. They sit at the lowest tier — Account, Flow, or Node values override them.

{{email}}Booking email address

{{phone}}Booking phone number

{{first_name}}Booking first name

{{last_name}}Booking last name

{{fullname}}Booking full name

{{address}}Booking street address (falls back to event address)

{{zip_code}}Booking zip code (falls back to event zip)

{{venue}}Event venue (falls back to booking venue)

{{event_name}}Event header / name

{{event_date}}Event date (ISO; uses startDateTime when present)

{{event_time_start}}Event start time (market-formatted: '6:00 PM' for UK/IE, '18:00' for DK/SE)

{{event_time_end}}Event end time (market-formatted: '9:00 PM' for UK/IE, '21:00' for DK/SE)

{{event_city}}Event city

{{event_address}}Event street address

{{event_id}}Event business ID (e.g. E-1629-CMP-03746)

{{foredragsholder}}Lecturer name (Danish: foredragsholder)

{{food_type}}Event food type (Dinner, Sweet Bites, ...)

{{webflow_url}}Webflow URL for the event page

{{booking_status}}Airtable booking status (Booked, Cancelled, ...)

{{civil_status}}Booking civil status

{{tickets_remaining}}Tickets remaining for this booking

{{platform_id}}Platform-specific booking ID

{{airtable_record_id}}Airtable booking record ID (rec...)

{{market_unit}}Market unit (e.g. DFJ_DK) — used as Salesforce Market_Unit__c

{{salesforce_lead_id}}Salesforce Lead ID from Airtable — used as SMS__c Record_ID__c

{{formatted_date}}Pre-formatted booking date string

{{date_time}}Market-specific formatted date+time (e.g. '11th of May at 6:00 PM to 9:00 PM' for IE/UK, '11. maj kl. 18:00 til 21:00' for DK)

{{start_time}}Alias for event_time_start (market-formatted: '6:00 PM' for UK/IE, '18:00' for DK/SE)

Salesforce SMS

SMS nodes create records on the Salesforce SMS__c object via REST. Authentication uses the OAuth 2.0 Client Credentials flow — enable it on the Connected App and assign a Run-As user. If any env vars are missing the SMS node falls back to a stub that only logs the payload (so local dev keeps working).

Required env vars

SALESFORCE_LOGIN_URL (defaults to https://login.salesforce.com)
SALESFORCE_CLIENT_ID / SALESFORCE_CLIENT_SECRET (Connected App)

SMS__c fields set by default

Direction__cOutgoing

Market_Unit__c{{market_unit}}

Message__c(from the node's Message Text)

Record_ID__c{{salesforce_lead_id}}

Send_From__cAlphanumeric Sender ID

Status__cPending

To_Number__c{{phone}}

Type__cAutomated

Override per-node under Salesforce Field Mapping in the SMS config.

System Settings

Configure automated reminder processing.

Reminder Check Interval

How often the system fetches events from Airtable and sends any due reminders