An AutomationTile represents a physical NFC chip and QR code tile that triggers actions in a Nexudus-powered coworking space. Each tile is linked to a single action (e.g. check-in, booking, door unlock, HTTP request) that fires when a customer scans or taps the tile.The Action field determines what happens when the tile is scanned. Some actions require additional data in ActionParameters:
Tiles can optionally be geo-fenced to restrict scanning to a physical area around the tile’s installed location. Enable EnableGeofence, set Latitude/Longitude, and choose a GeofencePrecission level. MaxDistanceMeters overrides the precision preset with a custom radius.Set CheckCustomerIn to also check the customer into the space when they scan the tile, regardless of the tile’s primary action.
This endpoint requires OAuth2 authentication. Include a valid bearer token in the Authorization header.
The authenticated user must be a full unrestricted administrator or have the AutomationTile-List role.
Filter by whether to restrict the tile to a geographic area. When enabled, the tile only works if the user is within the configured radius of the tile’s coordinates.
The list of AutomationTile records matching the query. See the Get one AutomationTile endpoint for the full list of properties returned for each record.
Partial records — The listing endpoint returns a summary representation of each AutomationTile. The following fields are not included in the Records[] response: Action, GeofencePrecission.To get all fields, fetch the full record using the Get one AutomationTile endpoint.Important for updates: When updating a record via PUT, always retrieve the full record with a GET request first, apply your changes to that complete data, and then send the updated record. Do not use data from a listing response as the base for a PUT request, as missing fields may be unintentionally cleared.