<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=5003644&amp;fmt=gif">
Skip to content
English - Australia
  • There are no suggestions because the search field is empty.

Momentum Nodes

What each Momentum node does and when to use it.

What is a Momentum Node?

You can think of a Node as a step in the workflow. Each node represents an action within the Momentum workflow (e.g. emails being sent, forms to be filled out and submitted, waiting periods applied).

The available node types are:

  • Trigger Nodes: Manual Creation, External Learning, New User Created, Course Enrollment, Course Completion
  • Form Nodes
  • Email Nodes
  • Wait and Junction Nodes: Wait Nodes, Junction Nodes
  • Assign Nodes: Assign Owner, Assign Cohort
  • User Management Nodes: Create User, Suspend User, Update External Learning, Enroll User, Mark User Completion
  • Terminal Nodes

Trigger Nodes

A trigger node defines how a Momentum application is started.

Manual Creation

The User Created Application trigger node starts the workflow when a user clicks the Start New Application button within the Momentum.

External Learning

The Created External Learning trigger node starts the workflow when an External Learning is created. If users create an External Learning from their My Learning page, an application is created in this Momentum workflow.

Note: you need to apply the External Learning form you want this to apply to within the Created External Learning node.

Creation of User

The On Create User trigger node starts the workflow when a new user is created. Consider this for your next onboarding or account setup Momentum.

Note: this node can also trigger when a user first logs in, including through SSO. Choose between user creation and first login in the node settings.

On Course Enrollment

The On Course Enrolment trigger node starts the workflow when a user enrolls in a Course (e.g. to remind users to complete the Course or send feedback requests).

This node can also sync multiple Course enrollments together (enrolling in one enrolls the user in them all), and chain multiple Momentums together if you use the node that enrolls users in a Course alongside this one.

On Course Completion

The On Course Completion trigger node starts the workflow when a user completes a Course (e.g. to enroll the user in follow-up content, send feedback requests, or notify administrators that users are completing specific content).

Form Nodes

The Form Node is a step where the assignee fills in a form. The node is a container for a form template you build separately.

Note: a form template must be published before it can be selected in a Form Node. Draft templates do not appear in the list. To publish, open the template and click Actions > Publish.

You can also set a due date on a Form Node and send reminder emails to the assignee until the form is submitted.

To build the form itself, see How to Create a Feedback Form Template.

Email Nodes

The Email Node sends automated emails to designated users at any point in the Momentum workflow (e.g. to notify applicants, administrators or supervisors when a form has been completed, or to tell a user about an action they need to complete).

Wait and Junction Nodes

Wait Nodes

The Wait Node holds applications until they are allowed through. Options for the waiting period are:

  • Cron - schedule intervals for when applications are allowed through (e.g. "On the second day of each month" or "Every Monday, Wednesday and Friday every two weeks").
  • Application Start Date - a set number of days, weeks or months after the application start date.
  • Node Entered Date - a set number of days, weeks or months after the application entered the Wait Node.
  • Application Owner Creation Date - a set number of days, weeks or months after the application owner's user account was created.
  • Constant Date - used with the Date Select field in a form. Set a number of days, weeks or months from a date selected in a form, from a static date, or from the user's enrollment or completion date.

Junction Nodes

The Junction Node does nothing by itself, but can have all the usual Momentum functionality attached. Use it in more complex Momentum setups to make chains of logic and transitions easier to set up and visualize.

Assign Nodes

Assign Owner

The Assign Owner node transfers the application to a different user within the workflow. Ownership can go to a fixed user each time, or be set dynamically from a user selection field in a form.

Assign Cohort

The Assign Cohort node adds a user to a set Cohort as part of the workflow (e.g. by role or department). Once a user passes through this node, they are placed in that Cohort, so you can target enrollments, communications or permissions to that group.

Create User

The Create User node creates a new user account when the application passes through it. The first name, last name and email address come from form fields earlier in the workflow.

Note: if your tenancy has Allow Separate Emails and Usernames turned on, the node also shows a required Username field, and it checks for existing users by username. Map a form field to Username in each Create User node, or the node will not create users. Existing workflows are not updated automatically when this setting changes.

Suspend User

The Suspend User node suspends a user account when the application passes through it (e.g. as part of a leave request form).

Update External Learning

The Update External Learning node updates an existing External Learning with new information. It can update any field using responses from the Momentum application or static values (e.g. to add an approval step so the External Learning is only marked complete once an administrator approves it).

Enroll User

The Course Enrolment node enrolls a user in a set Course when the application passes through it, so users are added to the right content without manual work.

Mark User Completion

The Course Completion node marks a user complete for a set Course when the application passes through it. The completion date can be the date of the transition, a fixed date, or a date selected in a form field.

Terminal Nodes

The Terminal Node marks the end of an application, either because it was rejected or because it completed successfully. Each Terminal Node can be labeled to show how the application ended.

Note: once an application reaches a Terminal Node it cannot be moved back into the workflow. Check approval routes and transition conditions before go-live. If an application ends in error, contact support.

Do reminders stop when a user is suspended?

No. Email and reminder nodes do not skip suspended users. If a user leaves, move or close their open applications so their supervisor stops receiving reminders.