Skip to content

Invoke a command from a command

One fantastic feature of PURISTA is that commands can trigger other commands from different services. This communication occurs through the event bridge.

This implies that the command initiating the action doesn't need to know where the other command is located.

To trigger another command, you must specify it in the command builder. By setting the input and output schemas, we ensure that data is handled correctly, preventing any unintended data from leaving or entering the command function.

import {  
} from './schema.js'

const invokePayloadSchema = z.object({ 
 inputValue: z.string() 

const invokeParameterSchema = z.object({ 
 someInputParameter: z.string() 

const invokeResponseSchema = z.object({ 
  resultValue: z.string() 

const myCommandBuilder = myServiceBuilder
  .getCommandBuilder('functionName', 'some function description', 'functionEventEmitted')
    'OtherServiceName', // the service name to invoke
    '1', // the service version to invoke
    'otherCommandName', // the command name to invoke
  .setCommandFunction(async function (context, payload, parameter) { 

    const invokePayload = {
      inputValue: 'some input payload'

     const invokeParameter = {
      someInputParameter: 'a parameter'

    const invokeResult = context.service.OtherServiceName['1']
      .otherCommandName(invokePayload, invokeParameter)
    // invokeResult is type of { resultValue: string }

You can use canInvoke as often as needed. Meaning you can invoke more than one other service command.


In the invoke schemas define only necessary data. Especially the response schema should only contain data, which is used by the command function.