| App Action | An app action is counted each time a workflow moves data or performs an action on your behalf. For example, let’s say your workflow has a Rippling trigger that creates a profile for a new employee on the Sales team in Salesforce. Once the profile is created, the workflow then sends an email to the new employee containing their Salesforce setup information. This would count as two (2) app actions each time the workflow is triggered. |
| Connector | Connectors are any app, logic or utilities used within a workflow. A connector may contain any number of app actions. |
| API | API stands for Application Programming Interface. Alloy's app partners create API's in order to integrate with Alloy and allow their data to be exchanged with data from other apps. This two-way exchange essentially means that you can "push" and "pull" data from one app into another. In Alloy, each connector within a workflow corresponds with one API "call," or action. |
| Connector Trigger | Connector triggers are simply connectors that are placed at the start of your workflow. Triggers are crucial to your workflows, as trigger connectors set workflows in motion. |
| Triggered Workflow | Triggered workflows are workflows that depend on a connector trigger. It will only take place when an event in one of your apps occurs and kicks off the workflow. |
| Automatic Workflow | Automatic workflows depend on an “on-off” switch that allows you to activate or deactivate them. Once activated, a workflow will run each time the trigger is set off. |
| Branch | The branch connector allow you to perform different paths of logic depending on the conditions you create for each branch. |
| Integration | Integrations refer to the 3rd party software tools that Alloy connects with. We use "integrations" and "apps" interchangeably. |
| Iterate | If you're technical, you may recognize Iterate as essentially a for loop. For nontechnical folks, Iterate connectors allow you to perform operations on each item in a list of items. For example, if you fetch a list of new customers in the last 90 days from Salesforce, you can add an Iterate connector right after to iterate through from a previous connector. |
| Manual Workflow | A manual workflow only runs when the user presses the “Run” button in order to trigger the workflow. Manual workflows are useful for running workflows at your discretion. |
| Recipe | Recipes are pre-built workflows available under the Marketplace tab in your dashboard. Recipes are sourced from our community and are a great starting point for new users as they only take a few minutes to set up. |
| Variable | Variables let you use the output from one connector as input for other connectors downstream in a workflow. Inputs refer to the fields you need to fill out when configuring a new connector. |
| Variable Selector | The variable selector shows a list of all possible data points for a given block. |
| Custom event | A Custom Event is used to invoke a workflow from your application and can be called via the Alloy Embedded REST API. You can associate multiple workflows with a single Custom Event. Whenever you trigger the Custom Event, every workflow with this event will be triggered. |
| Workflow Run | A workflow run refers to each time an entire workflow is run. This can include any number of actions within it. For example, if your workflow runs once every hour during a day, then there were 24 workflow runs. You can check notifications in the top right of the workflow editor for details on why a workflow may have failed. |