Automation Tiles connect the physical space to Nexudus. Customers perform actions — check in, unlock a door, book a resource, and more — by tapping their phone on an NFC tile or scanning its QR code. The Members Portal handles executing the tile action and displaying the result.
How it works
- A customer scans or taps an automation tile placed in your space.
- The portal opens a dedicated full-page URL for that tile (
tiles/:tileId/execute).
- The portal calls the API to execute the tile’s configured action.
- The customer sees the result — a success message, an error, or is redirected to a URL.
What customers see
Loading state
While the action is being processed, a loading indicator is shown with a “Please wait…” title.
Success
If the action completes successfully, a success alert is displayed along with the tile name.
Error
If the action fails, an error alert is shown. When the API returns a specific error message, that message is displayed. Otherwise a generic “Sorry, this tile does not seem to work” message appears.
Redirect
Some tile actions (e.g. RedirectUrl) send the customer to an external URL instead of showing a result on the page.
Tile actions
The action performed when a tile is scanned depends on how the tile is configured in the Nexudus dashboard. Common actions include:
| Action | Description |
|---|
| Check In | Checks the customer into the space |
| Check Out | Checks the customer out of the space |
| Booking Check In | Checks the customer into a specific booking |
| Event Check In | Checks the customer into a specific event |
| Unlock Door | Unlocks an access-controlled door |
| Book Resource | Opens a booking flow for a specific resource |
| Book Desk | Opens a booking flow for a desk |
| Redirect URL | Redirects to an external URL |
| Request URL | Sends a request to an external URL |
| Resource Cleaned | Marks a resource as cleaned |
Automation Tiles are managed from the Nexudus dashboard under Settings → Automation Tiles. Each tile has a unique ID and a configurable action.
API endpoint
The portal executes tile actions via:
GET /api/tiles/execute/{tileId}
Response
| Field | Type | Description |
|---|
tileName | string | Display name of the tile (optional) |
result.WasSuccessful | boolean | Whether the action completed successfully |
result.Message | string | Human-readable message from the server (optional) |
result.RedirectURL | string | If present, the customer is redirected to this URL instead |
Route
The tile execution page is available at:
/:webAddress/tiles/:tileId/execute
FullPageLayout — a minimal layout without the main navigation — so the customer sees only the action result. 
