Triggers, Steps, and Variables

Formulas are comprised of triggers that kick off formulas, steps that the trigger executes, and variables used to define inputs to the formula instance. The triggers, steps, and variables build up context that you can refer to as you build a formula. For example, a JS Script step might build a JSON payload that you can refer to in a later step as ${steps.stepName}. Within a formula's context, you can refer to steps as as ${steps.stepName}, variables as ${config.variableName}, triggers as ${trigger.triggerComponent} (such as ${trigger.args} or ${trigger.event}), and formula metadata as ${info.metadataName}. Make sure that the dollar sign is outside of the curly brackets (${steps.stepname} not $steps.stepName) and that you don't take any shortcuts like ${stepName}.

This section provides configuration information about each formula component.

Triggers

Triggers are the actions that kick off a formula. Triggers can be one of the following types:

• Event
• Element Request
• Scheduled
• Manual

Event

You can set up triggers that listen for an event to happen on an element instance. To set up this trigger, you must use an Element Instance Variable that, when specified in a formula instance, refers to an element instance that is configured to use webhooks or polling to listen for events.

To set up an Event trigger, you must specify an Element Instance Variable. Click to find or create a variable to represent the element instance that will kick off a formula instance when an event occurs.

If an Event trigger's Element Instance is set up for polling instead of webhooks, then each object that is found while polling triggers a separate formula execution. For example, if the poller finds five changes, five different formula executions kick off.

To see event triggers in action, see the following examples:

• CRM to Messages
• Add New Contact Created in One System to Another

Event Trigger Scope

Event triggers add step execution values like those described in the example JSON below to the formula context. The formula context is then passed from step-to-step, allowing you to use these values in any subsequent steps in your formula.

{
  "eventId": 11211123,
  "instanceId": 231232132,
  "type": "event",
  "event": {
    "date": "2016-06-01T04:09:10Z",
    "elementKey": "sfdc",
    "eventType": "UPDATED",
    "objectId": "n005i000003sgTd0AAE",
    "objectType": "Contact"
  }
}

Example references to Event trigger scope:

• ${trigger.event.objectType}
• ${trigger.event.eventType}

Element Request

Triggered any time a specific API call is made to a given Element Instance. To set up this trigger, you must use an Element Instance Variable that, when specified in a formula instance, refers to an element instance.

When you set up an Element Request trigger, specify the following parameters:

• Element Instance Variable: Click to find or create a variable to represent the element that will kick off a formula instance when the specified API call occurs.
• Method: The API method of the API call, such as GET, POST, PUT, PATCH, or DELETE. .
• API: The endpoint, such as hubs/crm/contacts.

Scheduled

Triggered at times specified by a Cron job. We recommend that you review the many reference pages for Cron jobs online.

In general, the Cron format consists of:

Examples

• Run every 15 minutes

      0 0/15 * 1/1 * ? *
  

• Run every Monday at noon

  0 0 12 ? * MON *
  

• 8.00 PM every weekday (Mon-Fri):

      0 0 8 ? * MON,TUE,WED,THU,FRI *
  

• midnight on 1st ,10th & 15th of month

  0 0 0 1,10,15 1/1 ? *
  

To see a Scheduled trigger in action, see Bulk Transfer CRM Data

Manual

Triggered via a manual API call to POST /formulas/instances/:id/executions. Manual triggers do not require any specific configuration. You can use formulas triggered manually as synchronous API calls. See Formula as a Resource for setup instructions.

To see a Scheduled trigger in action, see Bulk Transfer CRM Data

Step Types

You can choose from several different types of steps to make up your formula. You can refer to any step with the ${steps.stepName syntax}. Because you refer to the step by name, each step name must be unique within each formula. However, you can reuse a step name in a different formula.

You can use the following types of steps in your formulas:

• ActiveMQ Request
• Element API Request
• HTTP Request
• JS Filter
• JS Script
• Loop Over Variable
• Platform API Request
• Retry Formula on Failure
• Stream
• Sub-Formula

ActiveMQ Request

The ActiveMQ Request (amqpRequest) step type uses the AMQP protocol to post a message to an MQ server such as RabbitMQ.

When you set up an ActiveMQ Request step, include the following information:

ActiveMQ Request Step Scope

ActiveMQ Request steps add the step execution values described in the example JSON below to the formula context. The formula context is then passed from step-to-step, allowing you to use these values in any subsequent steps in your formula.

{
  "myAmqStep": {
    "request": {
        "body": "{\"message\":\"This is a test message.\"}",
        "url": "amqp://otqaqsml:tPpXwTl7-iMtezRmyJmD-y2U_XbroYpW@jaguar.rmq.cloudamqp.com/otqaqsml",
        "exchange": "main",
        "queue": "myqueue"
    }
  }
}

Example references to ActiveMQ Request scope:

• ${steps.myAmqStep.request}
• ${steps.myAmqStep.request.body}

Element API Request

The Element API Request (elementRequest) step makes an API call to a specific Element Instance.

To see an Element API Request step in action see:

• CRM to Messages
• Add New Contact Created in One System to Another
• Bulk Transfer CRM Data

When you set up an Element API Request step, include the following information:

Element API Request Step Scope

Element API Request steps add the step execution values described in the example JSON below to the formula context. The formula context is then passed from step-to-step, allowing you to use these values in any subsequent steps in your formula.

{
  "myElementRequestStep": {
    "request": {
        "query": "{}",
        "body": "{\"Name\":\"New Account Name\"}",
        "method": "POST",
        "path": "{}",
        "uri": "/elements/api-v2/hubs/crm/accounts",
        "headers": "{\"authorization\":\"Element /ABC=, User DEF=, Organization GHI\",\"content-length\":\"14\",\"host\":\"jjwyse.ngrok.io\",\"content-type\":\"application/json}"
    },
    "response": {
      "code": "200",
      "headers": "{\"Set-Cookie\": \"CESESSIONID=2CA15552EE56EAF65BF1102F6CACEACC;Path=/elements/;HttpOnly\"}",
      "body": "{\"Id\": \"001tx3WcAAI\", \"Name\": \"New Account Name\"}"
    }
  }
}

Example references to Element API Request scope:

• ${steps.myElementRequestStep.request}
• ${steps.myElementRequestStep.request.body}
• ${steps.myElementRequestStep.response.code}

HTTP Request

The HTTP Request (httpRequest) step make an HTTP/S call to any URL/endpoint.

When you set up an HTTP Request step, include the following information:

HTTP Request Step Scope

HTTP Request steps add the step execution values described in the example JSON below to the formula context. The formula context is then passed from step-to-step, allowing you to use these values in any subsequent steps in your formula.

{
  "myHTTPRequestStep": {
    "request": {
        "query": "{}",
        "body": "{\"Name\":\"New Account Name\"}",
        "method": "POST",
        "url": "https://api.myservice.com:443/myresource",
        "path": "{}",
        "headers": "{\"authorization\":\"mysessionid\",\"content-type\":\"application/json}"
    },
    "response": {
      "code": "200",
      "headers": "{\"Set-Cookie\": \"CESESSIONID=2CA15552EE56EAF65BF1102F6CACEACC;Path=/elements/;HttpOnly\"}",
      "body": "{\"id\": \"237648\", \"name\": \"My New Resource Name\"}"
    }
  }
}

Example references to HTTP Request scope:

• ${steps.myHTTPRequestStep.request}
• ${steps.myHTTPRequestStep.request.body}
• ${steps.myHTTPRequestStep.response.code}

JS Filter

Use the JS Filter (true/false) (filter) step to write custom Javascript that must return true or false. As with all steps, you must include a name. See Javascript in Formulas for more information about working with Javascript in formulas.

Use JS Filter steps to specify only certain event types, field values, or other information. You can also use filters to split formulas into different paths.

• If a filter returns true, the formula executes the left, or OnSuccess , step.
• If a filter returns false, the formula executes the tight, or OnFailure , step.

To see a JS Filter step in action see:

• Retrieve, Transform, and Sync Contact
• Bulk Transfer CRM Data

JS Filter Step Scope

JS Filter steps pass a boolean into the JS done callback function. That boolean is made available under the key titled continue, as shown in the examples below.

{
  "myFilterStep": {
    "continue": "true"
  }
}

{
  "myFilterStep": {
    "continue": "false"
  }
}

JS Script

Use the JS Script (script) step to write custom Javascript that must pass a valid JSON object to the done callback. As with all steps, you must include a name. See Javascript in Formulas for more information about working with Javascript in formulas.

Use JS Script steps to build objects to use in request steps for query parameters or the request body.

To see a JS Script step in action see:

• CRM to Messages
• Bulk Transfer CRM Data

JS Script Step Scope

JS Script steps add whatever object is passed to the JS done callback to the formula context. The formula context is then passed from step-to-step, allowing you to use these values in any subsequent steps in your formula.

done({
  foo: 'bar',
  object: {
    someKey: 'someValue'
  }
});

Example references to JS Script scope:

• ${steps.myScriptStep.foo}
• ${steps.myScriptStep.object}
• ${steps.myScriptStep.object.someKey}

Loop Over Variable

Use the Loop Over Variable (loop) step to loop over a list of objects from a previous step or trigger. Set onSuccess to the first step in the loop. When you have reached the last step in the loop set the onSuccess field to the loop step, this will restart the loop for the next object. If you need to continue on after the loop is completed, set onFailure to the next step to execute after the loop is completed. For a loop step, onFailure is executed when the loop has been executed for all objects in the list.

When you set up a Loop Over Variable step, include the following information:

Loop Over Variable Step Scope

Loop Over Variable steps make available the current object being processed and the index to each step executed inside of that loop. For example, if we have a loop step named looper, any steps that are run inside of that loop would have access to looper.index and looper.entry.

Example references to Loop scope:

• ${steps.myLoopStep.entry.id}
• ${steps.myLoopStep.index}

Platform API Request

The Platform API Request (request) step makes an API call to one of our platform APIs.

When you set up a Platform API Request step, include the following information:

Platform API Request Step Scope

Platform API Request steps add the step execution values described in the example JSON below to the formula context. The formula context is then passed from step-to-step, allowing you to use these values in any subsequent steps in your formula.

{
  "myPlatformStep": {
    "request": {
        "query": "{}",
        "body": "{\"Name\":\"New Account Name\"}",
        "method": "POST",
        "path": "{}",
        "uri": "/elements/api-v2/hubs/crm/accounts",
        "headers": "{\"authorization\":\"Element /ABC=, User DEF=, Organization GHI\",\"content-length\":\"14\",\"host\":\"jjwyse.ngrok.io\",\"content-type\":\"application/json}"
    },
    "response": {
      "code": "200",
      "headers": "{\"Set-Cookie\": \"CESESSIONID=2CA15552EE56EAF65BF1102F6CACEACC;Path=/elements/;HttpOnly\"}",
      "body": "{\"Id\": \"001tx3WcAAI\", \"Name\": \"New Account Name\"}"
    }
  }
}

Example references to Platform API Request scope:

• ${steps.myPlatformStep.request}
• ${steps.myPlatformStep.request.body}
• ${steps.myPlatformStep.response.code}

Retry Formula on Failure

Retry Formula on Failure (retryFormulaExecution) retries a formula instance execution with the same input data. You can configure the number of retry attempts, with a maximum of 7 attempts. The retry time is set based upon an exponential backoff in minutes. The equation used for the exponential backoff is round(e^x) where x is the retry attempt number.

When you set up a Retry Formula on Failure step, include the following information:

Retry Formula on Failure Step Scope

Retry Formula on Failure steps truncate the formula execution and schedule a retry execution for a later time based upon the retry attempt number. The result of this equation is used to schedule a retry in minutes. The step execution response value for this step is a string as shown in the example below.

{
  "id": "53067",
  "key": "retry.error",
  "value": "Formula instance execution scheduled for retry at approximately 2016-12-05T08:52:37-07:00"
}

In this example, the step name in the formula is retry, and the value of the step execution indicates the time when the formula execution will be retried.

Stream File

Stream File (elementRequestStream) steps move a file from one Element Instance to another. Stream Files steps configure two API requests instead of just one. One request downloads the date from an element instance, and the second request uploads the data to another. Use the response body of the download request as the request body of the upload request.

To see a Stream File step in action see Bulk Transfer CRM Data.

When you set up a Stream File step, include the following information:

Stream File Step Scope

Stream File steps add the step execution values described in the example JSON below to the formula context. The formula context is then passed from step-to-step, allowing you to use these values in any subsequent steps in your formula.

{
  "myStreamStep": {
    "download": {
        "request": {
              "query": "{}",
              "method": "POST",
              "uri": "/elements/api-v2/hubs/crm/accounts",
              "headers": "{\"authorization\":\"Element /ABC=, User DEF=, Organization GHI\",\"content-length\":\"14\",\"host\":\"jjwyse.ngrok.io\",\"content-type\":\"application/json}"
          },
          "response": {
              "code": "200",
              "headers": "{\"Set-Cookie\": \"CESESSIONID=2CA15552EE56EAF65BF1102F6CACEACC;Path=/elements/;HttpOnly\"}"
          }
      },
      "upload": {
          "request": {
              "query": "{}",
              "method": "POST",
              "uri": "/elements/api-v2/hubs/crm/accounts",
              "headers": "{\"authorization\":\"Element /ABC=, User DEF=, Organization GHI\",\"content-length\":\"14\",\"host\":\"jjwyse.ngrok.io\",\"content-type\":\"application/json}"
            },
            "response": {
                "code": "200",
                "headers": "{\"Set-Cookie\": \"CESESSIONID=2CA15552EE56EAF65BF1102F6CACEACC;Path=/elements/;HttpOnly\"}",
                "body": "{\"Id\": \"001tx3WcAAI\", \"Name\": \"New Account Name\"}"
            }
        }
    }
}

Example references to Stream File scope:

• ${steps.myStreamStep.download.request.query}
• ${steps.myStreamStep.upload.request.headers}
• ${steps.myStreamStep.upload.response.body}

Sub-Formula

Sub-Formula (formula) steps run another formula instance.

When you set up a Sub-Formula step, include the following information:

Sub-Formula Step Scope

Sub-Formula steps add the values produced as the result of the last step in the sub-formula. Therefore, we recommend that when you build formulas to be used by other other formulas that you add a specific step to aggregate and returns whatever data is needed in the parent's formula context.

If the sub-formula requires variables, then those variables can either be set in the parent formula instance using the same config names or passed in via the subFormulaConfigs property. All sub-formulas inherit their parent formula's configuration values. If you pass in the subFormulaConfigs these are added to the list of existing configs from the parent and the sub-formula has access to the parent's configs and those passed in with the values in subFormulaConfigs taking precedence.

The args can be accessed in the sub-formula using trigger.args. The subFormulaConfigs can be accessed in the sub-formula using config for example: ${config.crmInstanceId}.

Formula Variables

Formulas include two types of variables that you must specify when you run a formula instance:

• Element Instance Variable: A variable that is replaced by a specific element when you run a formula instance.
• Value Variable: A variable that is replaced by a configurable value when you run a formula instance.

Formula variables are limited to the formula and cannot have the same name. However, you can name variables in different formulas with the same name like "originInstance" or "destinationInstance."

Formula Variable Scope

Formula variables contribute to the formula context and you refer to them by their Formula Step Variable Name. This name is always config.variableName. So, if you create an Element Instance Variable called originInstance, you refer to it as ${config.originInstance}. A Value Variable called objectName is referred to as ${config.objectName}.