Utility Actions

Special-purpose actions for data collection, IoT integration, and user group management.

Form

The Form action collects user data through customisable form fields. This is a versatile action for registrations, surveys, giveaway entries, and general data collection. You can tailor the form to capture exactly the information you need by adding and configuring individual fields.

Form Fields

Fields are dynamically added and removed from the form. You can add as many fields as needed and reorder them to suit your requirements. Each field has the following configuration options:

  • Field Type — Choose from Full Name, First Name, Last Name, Email, Phone, Checkbox, Custom, or Custom Long Text. The field type determines the input control presented to the user and any built-in validation behaviour.
  • Display Name — The label shown to the user above the field in the app.
  • Field Name — The internal identifier used when storing and exporting the collected data.
  • Required — A toggle that marks the field as mandatory. Users will not be able to submit the form until all required fields have been completed.

Email fields automatically receive regex validation to ensure the submitted value is a properly formatted email address.

Form Settings

The following settings control the overall behaviour of the form:

  • Validate Input — Enable field validation to check submitted values against the rules defined by each field type.
  • Allow Multiple Entries — When enabled, users can submit the form more than once. This is useful for scenarios such as repeated giveaway entries or ongoing feedback collection.
  • Auto-expand on Load — When enabled, the form automatically expands when the stack loads, so users see the form fields immediately without needing to tap to open the action.

Header Image

You can set an optional header image for the form. When a header image is configured, it replaces the action title in the app, providing a more visually engaging presentation. Use the CMS image selector or upload a new image to set the header.

Post Submission Content

After a user successfully submits the form, a confirmation message is displayed. You can configure this message using the following fields:

  • Submission Heading Text — The heading displayed on the confirmation screen after the form has been submitted.
  • Submission Body Text — The body text displayed beneath the heading, providing additional context or a thank-you message.

IoT Busyness Status

The IoT Busyness Status action displays real-time busyness information sourced from IoT sensors. This is useful for showing venue occupancy, queue lengths, or other capacity-related metrics to your audience. The action is configured with the following options:

  • Image — Upload an image to display alongside the busyness indicator. This could be a photo of the venue, area, or facility being monitored.
  • Link URL — An optional URL to link to. When set, users can tap the action to navigate to the specified address for more information.
  • Device UUID — Select from the list of available IoT devices registered on the platform. The selected device provides the real-time busyness data displayed by this action.
  • Graph Options — Choose the time period for the busyness graph. Available options include day, week, and month, allowing you to show historical busyness trends over different intervals.
  • Busyness Graphic — Toggle the visual busyness indicator on or off. When enabled, a graphical representation of the current busyness level is displayed to users.

Add User to Group

The Add User to Group action silently adds authenticated users to a specified fan group when they view the stack containing this action. This enables automatic group assignment based on stack interaction, without requiring any manual action from the user.

Configuration requires the following:

  • Fan Group UUID — Select from the list of available fan groups. Only groups that have self-registration enabled are shown in the selection list.

This action has no visible UI in the app. It runs in the background when a logged-in user views the stack. Use it for automatic group assignment based on stack interaction.