Actions usually contain the logic for processing the payload of the messages received by the service (through its listeners). Alternatively, an action may contain the transformation or routing logic for messages to be consumed by an external service or entity. A service must always have a list of one or more actions. Actions generally act as templates, therefore requiring you to set external configuration options in order for them to work.