Available Actions

This page lists the 18 built-in actions offered for a workflow Action step. Actions are grouped by the records they affect.

Column definitions:

Action — the name shown in the builder
Record — the record type the action targets (or creates)
Type — whether this action creates a new record or mutates (changes) an existing one
Bulk safe — whether this action can safely run as part of a bulk or fan-out operation

Member actions

These actions affect member records.

Action	Record	Type	Bulk safe	Parameters
Add member	Member	Create	No	First name, last name, member type (required); email, phone, birthday, sex, family status, Can manage own account, lead status, program of interest, lead details, lead source
Edit member	Member	Mutate	No	First name, last name, email, phone, birthday, sex, family status, member type, lead status
Send message	Member	Mutate	Yes	Template (required), message type (required, email or SMS)
Add note	Member	Mutate	Yes	Title (required), note text (required)
Delete member	Member	Mutate	No	—

The workflow picker excludes browser-only redirect actions. Edit member here is the background update action, not the action that opens a member’s edit page.

Configure Add member

Select Add member in an Action step. It creates a new profile rather than changing the workflow’s existing record.
Fill in First name, Last name, and Member type. Use the reference picker to take values from the workflow record or an earlier step.
Add optional contact and profile details. If your school uses lead management and the type is Lead, also choose Lead status. Program of interest, further details, and source apply only to leads; other member types ignore those lead details.
Connect any later steps. The new member’s ID and profile fields are available as references.

The usual member validation rules still apply, including valid contact details and checks for an email address or phone number already in use at your school. Creating a profile does not create a membership or subscription. An Add member step can create another profile each time it runs, so check the trigger and avoid repeated runs for the same person.

Who receives Send message?

The action includes the member and linked contacts with Receive Communications or Can Manage enabled, using the chosen email or SMS channel. It is not limited to the member’s own address. People without that contact method are omitted; if nobody has it, validation fails.

Shared addresses can be combined, while member-specific placeholders can require separate copies. Choose member placeholders for the student and contact placeholders for the recipient. SMS requires school SMS setup and a Rich Text template; Email Builder templates are email-only. Workflow messages do not bring archived conversations back into the main Inbox.

A successful message step means the send was accepted for processing, not that every recipient received it. Check the Outbox for delivery and suppression results.

Membership actions

These actions affect membership records (a member’s enrolment in a program).

Action	Record	Type	Bulk safe	Parameters
Create membership	Member	Mutate	No	Program (required), level, status (required), waiver handling, sessions remaining
Edit membership	Membership	Mutate	No	Program (required), level, status (required), sessions remaining, last promotion, next promotion override
Promote to next level	Membership	Mutate	Yes	Promotion date

Invoice actions

These actions affect invoice records.

Action	Record	Type	Bulk safe	Parameters
Create invoice	Invoice	Create	No	Member, due date (required), notes, receipt email
Edit invoice	Invoice	Mutate	Yes	Due date (required), notes, receipt email
Open invoice	Invoice	Mutate	Yes	—
Void invoice	Invoice	Mutate	Yes	—
Send receipt email	Invoice	Mutate	Yes	Email address (required)

Booking actions

These actions affect booking records.

Action	Record	Type	Bulk safe	Parameters
Create booking	Booking	Create	No	Member (required), session (required), date (required), trial, notes
Cancel booking	Booking	Mutate	Yes	Cancellation reason
Mark attendance	Booking	Mutate	Yes	Status (Attended or No show — required)

Member note actions

These actions affect notes on member profiles.

Action	Record	Type	Bulk safe	Parameters
Edit note	Member Note	Mutate	No	Title (required), note text (required)
Delete note	Member Note	Mutate	No	—

Using references in parameters

When filling in an action’s parameters, you can pull values from the triggered record or from earlier steps:

Select the [$] reference picker and choose a field from This record to use a current value from the run’s record.
Choose an earlier step’s output in that picker to use a field returned by an action or Read. For example, use the new invoice’s ID as the target of an Open invoice action.

References to the current record are read when the action executes. Earlier-step references use that step’s saved output, not a fresh lookup. Typing a placeholder-looking phrase into a plain-text field does not create one of these references. Missing fields or outputs can fail the step, so test each path before enabling a workflow for real members.

Next steps

Steps — how to use Action steps in your workflow
Trigger Events Reference — event types for the Action Event Occurs trigger
Create Your First Workflow — guided tutorial