Skip to Content
AutomationsActions

Access and devices

Control access, power, NFC tags and tablets from an automation.

Last updated on

These actions affect the park itself: who gets in, which meters have power and what tablets do. See Access control for the background on access methods. For how the outputs work, read Outputs of an action.

Create access method

Gives a customer access via a QR code, licence plate, PIN code or NFC.

FieldWhat you enter
CustomerThe id of the customer, for example {reservation.customerId}. Required
TypeQR code (default), License plate, PIN code or NFC
ValueThe licence plate or the NFC number. Leave empty for a QR code or PIN code, because Tillor creates those itself
Valid fromA date variable, for example {reservation.checkIn}. Empty means no limit
Valid untilA date variable, for example {reservation.checkOut}. Empty means no limit

For License plate and NFC, Value is required. The action provides {createdAccessMethod.id} and {createdAccessMethod.value}. The value is the code of the QR code or the PIN code. With the id you can then send the code via Send or print QR code.

Update access

Blocks, unblocks or extends an access method, or all access methods of a customer.

FieldWhat you enter
WhichOne access method (default) or All of a customer
Access methodOnly with One access method: the id, for example {createdAccessMethod.id}. Required
CustomerOnly with All of a customer: the id of the customer, for example {occupation.customerId}. Required
StatusLeave as it is (default), Active, Soft blocked, Blocked or Inactive
Valid untilA date variable. Empty keeps the current end date

Keep in mind:

  • If you leave Status on Leave as it is and Valid until empty, the step does nothing
  • With All of a customer, access methods set to Do not extend automatically keep their end date, just as happens when a customer pays an invoice. Their status does change. With One access method the step does change the end date, even if that access method is set to Do not extend automatically

Send or print QR code

Sends a QR access code to the customer, prints it, or both.

FieldWhat you enter
Access methodThe id of the access method. {createdAccessMethod.id} by default. Required
Send by e-mailOn by default
Send by text messageOff by default
Send by WhatsAppOff by default
PrintDo not print (default), Label printer or Receipt printer

If you switch off all three channels and choose Do not print, the step does nothing.

Open or close barrier

Opens or closes a barrier or gate.

FieldWhat you enter
Access pointChoose one of your access points. Required
ActionOpen (default) or Close

Switch power

Switches the power of a smart meter on or off. For example, to switch the power off when an occupancy ends.

FieldWhat you enter
Which metersEvery switchable meter of a terrain (default) or One meter
TerrainOnly with Every switchable meter of a terrain: the id of the terrain. {occupation.terrainId} by default. Required
MeterOnly with One meter: choose the meter. Required
PowerOn or Off. Off by default

Keep in mind:

  • With Every switchable meter of a terrain the step only switches the meters that can switch. If the terrain has none, nothing happens
  • If switching a meter fails, the step fails. With One meter that also happens if the meter cannot switch. Meters that were already switched before stay switched

Update NFC tags

Updates all NFC tags of a customer.

FieldWhat you enter
CustomerThe id of the customer, for example {occupation.customerId}. The action applies to every NFC tag of this customer. Required
ActionBlock (default), Unblock, Top up or Send low balance message
AmountOnly with Top up: the amount in euros, per tag. Must be greater than 0. Required

If the customer has two tags and you enter 20, each tag gets 20 euros added. Without tags the step does nothing. If the amount is not a number above 0, the step fails.

Control tablet or kiosk

Sends a command to a tablet or kiosk.

FieldWhat you enter
DeviceChoose the device. Required
CommandWake (default), Sleep, Reload, Identify or Play test sound

Set slideshow

Sets the slideshow on every tablet and kiosk, or on one device. The rest of the device settings stay as they are. If the same slideshow is already on a device, that device is skipped.

An hourly trigger, then an API request to an activities feed, and then this step: that is how you replace a separate synchronisation. Connect the step to the Succeeded output of the request.

FieldWhat you enter
DevicesEvery tablet and kiosk (default) or One device
DeviceOnly with One device. Required
ModeScreensaver (default, after a period without touch) or Background
Seconds per photoHow long one photo stays. 10 by default. From 3 to 600
Idle before it startsOnly with Screensaver: seconds without touch. 15 by default
FitFill or Fit inside
PhotosFrom a previous request (default) or Addresses
Image addressesOnly with Addresses: one https address per line. Required
ListPath of the JSON list, without braces. After an API request that is response.data. Required
Image fieldName of the field with the https address, for example signage_image. Required
Id fieldKeeps the same id for the same photo, so an unchanged list does not send a new message to the device
Status field and StatusOnly rows where that field has this value, for example CONFIRMED
Skip when setRows where this field has a value are dropped, for example deleted_at
Date field and End date fieldA row stays until that moment has passed. If the end date is empty, the date counts
Sort fieldSorts the list ascending, for example by date
Maximum photos5 by default, at most 20

An address that does not start with https:// is not counted. If the list is not a JSON array, the step fails and the current slideshow stays in place.

Was this page helpful?

On this page