Customer & Sales package

Event registration

A themed registration form with an event lookup, capacity check and waitlist, confirmation emails and an organiser task for special requests.

OfficialNo integrations neededStarts from a formStarter~10 min setupv1.0.1
Download .utpkg 14 KBHow to install

About this package

What it does

Event registration runs sign-ups for breakfasts, webinars, workshops and customer evenings from one form. The Events table holds each event with its date, venue and capacity; the Event registration form lists the open events and fills in the date, start time and venue when one is picked. Attendees add their details, dietary needs and any accessibility or special request.

Registering shows a success screen with the reference and starts the workflow through its Form submitted trigger. It counts the confirmed registrations for the event in the Registrations table: while there is room the attendee is confirmed and emailed; once the event is full they join the waitlist with their position.

Special requests from confirmed attendees go to the organiser as a task with Confirm and Decline buttons, a reply that is emailed to the attendee, a reminder and escalation. Every registration, waitlist place and request answer is in the Registrations table for name badges and catering numbers. Everything is built in.

Starts from a form

Starts from a form page: share the Event registration form (/f/<id>) on your website or invitations; each registration starts the workflow.

Someone fills in a form to start it: the workflow start form (Run dialog in the app, or your own portal posting to the API) or a standalone form page (/f/<id>) whose Form submitted trigger starts the workflow. People complete User Task forms along the way.

The flow

Step by step

  1. 1

    Register

    The form lists open events; the date, time and venue fill in, and the attendee adds dietary needs and requests.

  2. 2

    Success screen

    Register shows a success screen with the reference; the Form submitted trigger starts the workflow.

  3. 3

    Capacity check

    Confirmed registrations for the event are counted against its capacity.

  4. 4

    Confirm or waitlist

    With room the attendee is confirmed; otherwise they join the waitlist with their position. Both are emailed.

  5. 5

    Special requests

    The organiser confirms or declines each special request; the reply is emailed and recorded.

Event registration — A registration from the form: the event's confirmed places are counted against its capacity, the attendee is confirmed or waitlisted and emailed, and special requests go to the organiser. The same canvas you get in the designer after installing.

Forms

The start form and the task forms

People start it from a form page (/f/<id>) with its own header, theme and buttons; submitting it starts the workflow. User Tasks show their fields and outcome buttons to the assignee.

Form page · /f/<id>

Event registration

Register for an event · 3-column grid · own header and theme · Its own page: share the link or open it on a tablet

Event * event · lookup
Date event_date · dateYYYY-MM-DD
Starts event_time · text
Venue event_venue · text
Full name * name · text
Email * email · emailname@company.com
Company company · text
Job title job_title · text
Dietary requirements * dietary · choice
NoneVegetarianVeganGluten freeDairy freeHalal+3
Accessibility needs or special requests special_request · textarea
I agree to my details being used to manage this event * consent · boolean
Send me news about future events updates · boolean
Register

User Task

Organiser reviews the request

Special request from {{form.name}}: {{event_row.title}} · 2-column grid · own header and theme

Reply to the attendee * reply · textarea
Arranged with (venue, caterer…) arranged_with · text
Extra cost cost · currency
ConfirmDecline

From your code

Start a run over the API

Every workflow can be started over REST, MCP or the CLI, whatever its trigger, with the sample input below. Runs start straight away on the published version; replace <workflow id> with the id the install created.

REST

shell
curl -X POST "$USERTASKS_URL/api/v1/workflows/start" \
  -H "Authorization: Bearer $USERTASKS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"workflow_id":"<workflow id>","variables":{"event":"EVT-BRK-1119","name":"Priya Shah","email":"priya.shah@example.com","company":"Fabrikam Logistics","job_title":"Head of Operations","dietary":"Gluten free","special_request":"I use a wheelchair: is there step-free access and a table near the entrance?","consent":true,"updates":false}}'

CLI

shell
usertasks workflows inputs <workflow id>          # the start form: keys, types, required
usertasks workflows run <workflow id> --input event=EVT-BRK-1119 --input name="Priya Shah" --input email=priya.shah@example.com --input company="Fabrikam Logistics" … --wait

What's included

7 assets, ready to adapt

TypeNameDetails
Email templateRegistration confirmedSent to the attendee when they have a place.
Email templateRegistration waitlistedSent when the event is full and the attendee goes on the waitlist.
Email templateSpecial request answeredSent to the attendee with the organiser's answer to their special request.
Data tableEventsEvents people can register for. Capacity caps confirmed places; extra registrations go on the waitlist. Set status Closed to take an event off the form.
Data tableRegistrationsEveryone who registered: confirmed or waitlisted, their dietary needs and any special request and its answer.
formsEvent registrationRegister for one of our upcoming events. Pick the event; the date and venue fill in.
WorkflowEvent registration20 steps — A registration from the form: the event's confirmed places are counted against its capacity, the attendee is confirmed or waitlisted and emailed, and special requests go to the organiser.

Events · 5 sample rows

CodeEventDateStartsVenueCapacityOrganiserOrganiser emailStatusAbout

Registrations · 2 sample rows

ReferenceEvent codeEventDateNameEmailCompanyJob titleDietarySpecial requestRequestReply to the requestStatusRegistered

Requirements

What you connect it to

Credentials never travel in a package. The install wizard asks for what your environment must provide, or installs it incomplete until you finish setup.

Needs

  • Email (optional) — Email delivery configured for the instance (EMAIL_PROVIDER), used for notifications.

After installing

  1. Nothing to configure: install it and share the Event registration form from Forms (it works for signed-in users; publish it publicly if your workspace allows public forms).
  2. Replace the sample rows in Events with your events (code, title, date, start time, venue, capacity, status Open).
  3. Special requests go to the person who installed the package (the organiser). Change the assignee on "Organiser reviews the request" to route them elsewhere.
  4. Optional: set EMAIL_PROVIDER so confirmations, waitlist and request emails are delivered.

Asked for on install

Nothing: it installs complete.

Install

Install it in your workspace

Works on UserTasks cloud and on any self-hosted instance. Installing creates the assets above; nothing runs until you complete setup and start it.

In the app

  1. Download event-registration-1.0.1.utpkg.
  2. Open Automations → Packages and drag the file onto the page (or choose Import package). Browse gallery there lists every gallery package without downloading by hand.
  3. Pick the file. The wizard verifies the checksum, every file hash and the signature, and shows the readme.
  4. Review the changes (what is created) and the data rows.
  5. Fill in the requirements, or tick Keep incomplete and finish later with Complete setup.
  6. Done: the workflow is published and active once setup is complete.

With the CLI

shell
curl -fLO https://usertasks.com/gallery/event-registration-1.0.1.utpkg
usertasks packages inspect event-registration-1.0.1.utpkg       # offline: checksum, hashes, signature
usertasks packages install event-registration-1.0.1.utpkg --dry-run
usertasks packages install event-registration-1.0.1.utpkg       # prompts for each requirement
usertasks packages install event-registration-1.0.1.utpkg --keep-incomplete --yes   # in CI; finish with:
usertasks packages complete event-registration -f values.yaml

Verify the download

File SHA-256
465e771f06d69c969461d35bdef5348b6a974cbb4a241696e32367998b591177
Package checksum (what is signed)
sha256:fe987e8d31e9a60933f46dc677dffb69b989e3ae2ce555d113377432dd61b108
Signer
Unsigned preview build — compare the SHA-256 above

shasum -a 256 event-registration-1.0.1.utpkg should print the file SHA-256. How gallery packages are signed.

Versions

Version 1.0.1

  1. v1.0.12026-10-28Steps for the coordinator who set the package up are assigned to the workflow owner (workflow_owner_id), now that workflow_started_by names the person who started the run.
  2. v1.0.02026-10-28First release.

Installing a newer version upgrades in place: local credentials and requirement values are kept, and changes you made are flagged first. How packages work

More packages

Related

Browse the whole gallery