Concepts

Actions vs Scripts

Actions are built on top of scripts. An action tells Atlas when to do something. Its script tells Atlas what to do.

For example, a Slash Command action called hello runs when a member uses /hello. Its script can use the member who ran the command and prepare a reply:

{responder.text;Hello {user.name}!}

The flow is: a member runs /hello → the action's trigger provides context → the script runs → Atlas responds.

Scripts are reusable building blocks. You will also see them in plugin settings, such as a level-up message or a feed delivery template. The available tags depend on the context. A message action has a {message}. A feed script has a {$feedItem}.

Read Actions to create one, or Scripts to learn the syntax used inside one.