Notifications Tokens
  • 09 May 2024
  • 10 Minutes to read

Notifications Tokens


Article summary

Notifications tokens are a great way to customize automated messages you send to your customer. Each token is linked to a field available in each customer's account. You just need to add the relevant tokens in your notifications and every time Nexudus sends an email template, message macro or direct message to a customer via email, the token is automatically replaced by the value of the corresponding field in the customer's account.

For example, if you add "Hello {firstname}, " at the start of all your message macros and send them to a customer named John Doe, he'll receive a message starting with "Hello John, ". If you send your macros to another customer named Jane Meade, she'll receive a message starting with "Hello Jane, ".

You can add most of the tokens to the following notifications:
We replace tokens with a blank space or a dash if the field linked to the token is blank in Nexudus.

For example, if you add {accesscardtag} to a notification and a customer receiving it has no access card on file, they will see a blank space where the access card number should have been.

Universal Tokens

Universal tokens work in any of the following, provided the record you're trying to include email template, message macro,


{accessCardId}

Customer PIN code.

{accesscardtag}

Customer access card number. If they have more than one on record, they're all included by default.

{accesstoken}

Access token available for customers and visitors to connect to your wifi network.

This token only works in the following email notifications:
  • Booking confirmation
  • Booking confirmation for Visitors
  • Visitor registered

{address}

Customer address.

{afterEventNotificationText}

If you've enabled the option to send a message to customers as soon as an event they've attended ends via the event's record on the Admin Panel, the customer receives the message you've defined.

{androidurl}

URL of the Passport app or its white-label equivalent on the Google Play store.

{attendeeFullName}

Name of the customer who purchased tickets for an event.

This token only works in the following email notifications:
  • Event attendee event finished
  • Event comment posted
  • Event registration
  • Event registration cancelled
  • Event reminder
  • Event update
  • Event waiting list registration
  • Event waiting list update

{billingadress}

Address of the customer's billing address.

{billingcityname}

City of the customer's billing address.

{billingname}

Name in the customer's billing address.

{billingpostcode}

Post code of the customer's billing address.

{billingstate}

State of the customer's billing address.

{businessavatar}

URL of your space logo.

{businesscontactphone}

Your space's phone number.

{businesscontactweb}

Your space's website.

{businessaddress}

Your space's address.

{businesscontactphone}

Your space's phone number.

{businesscontactweb}

Your space's website.

{businessid}

Your space's location number in Nexudus.

This token is only suitable for messages that you send other admins since it is an internal ID.

{businessname}

Your space's name.

{calendarEventName}

Name of the event the customer is attending or has already attended.

This token only works in the following email notifications:
  • Event attendee event finished
  • Event comment posted
  • Event registration
  • Event registration cancelled
  • Event reminder
  • Event update
  • Event waiting list registration
  • Event waiting list update

{calendarEventNotes}

Notes added to the event the customer is attending or has attended.

This token only works in the following email notifications:
  • Event attendee event finished
  • Event comment posted
  • Event registration
  • Event registration cancelled
  • Event reminder
  • Event update
  • Event waiting list registration
  • Event waiting list update

{calendarProductName}

Name of the event ticket purchased or requested by the customer.

This token only works in the following email notifications:
  • Event attendee event finished
  • Event comment posted
  • Event registration
  • Event registration cancelled
  • Event reminder
  • Event update
  • Event waiting list registration
  • Event waiting list update

{calendarProductNotes}

Notes added to the event ticket purchased by the customer.

This token only works in the following email notifications:
  • Event attendee event finished
  • Event comment posted
  • Event registration
  • Event registration cancelled
  • Event reminder
  • Event update

# {calendarEventStartDate} & {calendarEventEndDate}
Start and end dates of an event the customer is attending or has already attended.

This token only works in the following email notifications:
  • Event attendee event finished
  • Event comment posted
  • Event registration
  • Event registration cancelled
  • Event reminder
  • Event update
  • Event waiting list registration
  • Event waiting list update

{cancellationdate}

Customer contract cancellation date if they have any scheduled plan cancellation.

The notification/message includes a dash if there's no cancellation date scheduled.

{cityname}

City in the customer's billing address details.

{code}

Brivo OnAir code that customers can use to unlock Brivo doors based on their purchases.

This token only works in the Brivo OnAir code notification.

{companyname}

Customer's company name.

{contracterms}

Terms and conditions defined in the Legal tab of the plan used to generate the customer's primary contract.

{contracterm}

Customer's current main contract. It only includes their primary contract by default.

{coworkerid}

Customer's ID in Nexudus.

This token is best suited for messages that you send other admins as it is an internal ID.

{coworkerpublicurl}

URL of the customer's page in the Members Portal directory.

This link only works if your Members Portal has the directory feature enabled.

{coworkerurl}

URL of the customer record on the Admin Panel.

{contractnotes}

Notes included in the customer's primary contact.

{custom1 to 30}

Public customer-related custom field that you've created.

Don't know which custom field number corresponds to the field you want to include in your message?

Just export all your custom fields and find the number of the custom field you want to include by looking up the CustomFieldIndex column.

{date}

Date that defaults to the day when the notification is sent.

For example, if customers receive your notification on August 1st, the token value would be August 1st.

{desk}

Any desk assigned to the customer either directly or via any active contract. This token will be blank if no desk is assigned to the customer receiving the message.

{due}

Amount of the invoice due for the customer.

This token only works in the following email notifications:
  • Invoice created
  • Payment received
  • Payment failed

{dueinvoicescount}

Number of due invoices in the customer's account when the notification is sent.

{dueinvoicenumbers}

Invoice reference of all the due invoices in the customer's account when the notification is sent.

{dueinvoicestotal}

Total invoice amount due in the customer's account when the notification is sent.

{earliestduedate}

Date of the latest invoice issued for the customer.

{email}

Customer's email address.

{filedescription}

Description fo the file the customer receives.

This token only works in the following email notifications:
  • Customer file sent
  • E-signature request

{filename}

Name of the file the customer receives

This token only works in the following email notifications:
  • Customer file sent
  • E-signature request

{firstname}

Customer's first name.

{fromTime}

Start time of a customer booking.

This token only works in the following email notifications:
  • Booking cancelled
  • Booking cancelled for visitors
  • Booking confirmation
  • Booking confirmation for Visitors
  • Booking reminder
  • Booking termination confirmation

{fromfullname}

Name of the user who posted a message on a discussion board.

This token only works in the New wall message email notification.

{fullname}

Customer's first and last name.

{gocardlesssignupurl}

Link for GoCardless direct debit mandate request. This is only relevant for customers who don't have a Gocardless mandate on their account already.

This token doesn't work unless:
  • You already enabled GoCardless as one of your payment methods.
    and
  • Made sure all relevant customers have it enabled in their account.

{invoicenumber}

Reference number of the invoice or credit note being issued to the customer.

This token only works in the following email notifications:
  • Credit note issued
  • Invoice created
  • Payment received
  • Payment failed

{invoicepaiddate}

Date when the customer paid their last invoice.

This token only works in the following email notifications:
  • Invoice created
  • Payment received
  • Payment failed

{invoicepaydate}

Latest invoice due date.

This token only works in the following email notifications:
  • Invoice created
  • Payment received
  • Payment failed

{invoicedperiod}

First day of the customer's primary contract invoice period.

{iosurl}

URL of the Passport app or its white-label equivalent on the Apple store.

{keyFobNumber}

Number stored in the key fob field of the customer's account.

This field is only relevant if you use Doorflow as your access control system.

{logoImage}

Your space's logo.

{nextbillingdate}

Customer's next invoice date. If the customer has multiple active contracts, it defaults to the closest invoice date when you send the notification or message.

{nextinvoicedate}

Customer's primary contact next invoice date.

{nextpriceplan} or {nexttariffname}

Name of all the plans that the customer has an active contract for at the time you send the notification.

{notes}

Public notes added to the Customer notes field of a customer booking.

This token only works in the following email notifications:
  • Booking cancelled
  • Booking cancelled for visitors
  • Booking confirmation
  • Booking confirmation for Visitors
  • Booking reminder
  • Booking termination confirmation

{paid}

Date when the customer's invoice was paid.

This token only works in the following email notifications:

your content goes here

{papercutusername}

Customer's email address that they should use alongside their PIN code to release print jobs if your space uses PaperCut.

{phone}

Customer's phone number.

{postcode}

Post code of the customer's address details.

{resetpasswordurl}

Link that the customer can click on to reset their password to access the Members Portal.

{resourceName}

Name of the resource booked by the customer.

This token only works in the following email notifications:
  • Booking cancelled
  • Booking cancelled for visitors
  • Booking confirmation
  • Booking confirmation for Visitors
  • Booking reminder
  • Booking termination confirmation

{salutation}

Customer's first name by default. You can easily edit this via the Account tab of any customer record. Customers can also update this field by logging in to the Members Portal or the Passport app.

2022-08-01_12h02_03.gif

{state}

State of the customer's address details.

{tariffname}

Name of the customer's primary contact. It is always identical to the plan used to create the contract.

{tariffprice}

Price of the customer's primary contact.

{terms}

Adds your space's full general terms and conditions.

{time}

Time when the notification was sent to the customer.

{timezone}

You space's time zone.

{tomorrow}

Date that defaults to the day after the day when the notification is sent.

For example, if customers receive your notification on August 1st, the token value would be August 2nd.

{total}

Total amount of the invoice issued for the customer.

{unpaidinvoicescount}

Total number of unpaid/due invoice references in the customer's account when the notification is sent.

{unpaidinvoicenumbers}

List of all unpaid/due invoice references in the customer's account when the notification is sent.

{unpaidinvoicestotal}

Total amount of all unpaid/due invoices in the customer's account when the notification is sent.

{userid}

ID of the user in your Nexudus account.

This token is only suitable for messages that you send to other admins since it is an internal ID.

{postcode}

Post code of the customer's address details.

{priceplan}

Price of the customer's current primary contract.

{pricewithcredits}

Price of the booking minus any credits applied to the booking.

{time}

Time when the notification is sent.

{toTime}

End time of a customer booking.

This token only works in the following email notifications:
  • Booking cancelled
  • Booking cancelled for visitors
  • Booking confirmation
  • Booking confirmation for Visitors
  • Booking reminder
  • Booking termination confirmation

{total}

Total amount of the invoice or credit note issued for the customer.

This token only works in the following email notifications:
  • Credit note issued
  • Invoice created
  • Payment received
  • Payment failed

{visitorcode}

PIN code assigned to the visitor to let them check in on their own using NexIO.

This token only works in the following email notifications:
  • Tour request confirmation
  • Booking cancelled for visitors
  • Booking confirmation for visitors
  • Visitor arrival
  • Visitor registered

{visitorexpectedarrivaldate}

Time and date when a registered visitor is expected in the space.

This token only works in the following email notifications:
  • Tour request confirmation
  • Booking cancelled for visitors
  • Booking confirmation for visitors
  • Visitor arrival
  • Visitor registered

{visitorfullname}

Name of the visitor.

This token only works in the following email notifications:
  • Tour request confirmation
  • Booking cancelled for visitors
  • Booking confirmation for visitors
  • Visitor arrival
  • Visitor check-in
  • Visitor registered

{visitorterms}

Adds your space's full visitor terms that you can edit via Settings > Legal terms and policies > Visitor terms on the Admin Panel.

This token only works in the following email notifications:
  • Tour request confirmation
  • Booking cancelled for visitors
  • Booking confirmation for Visitors
  • Visitor arrival
  • Visitor check-in
  • Visitor registered

{yesterday}

Date that defaults to the day before the notification is sent.

For example, if customers receive your notification on August 1st, the token value would be July 31st.

{zoom}

Link to join the connected Zoom meeting. This token only works for events and bookings that have Zoom links enabled.


Was this article helpful?

What's Next
Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.