# Setup your recipe
Once you start to create a new recipe, you will be taken to the set up page where you can get started.
Enter a name for your recipe or proceed to let the system choose a name for your recipe. You will also be able to select a folder in which to store your recipe.
Choose a recipe starting point
Select a starting point as an initial template for your recipe and click on ‘Start building’. Choose from the available templates below.
Triggers are the starting point for a recipe. A trigger can respond to events that occur in apps (e.g. Salesforce, JIRA) or run on a pre-defined schedule.
|1. Trigger from an app||Triggers determine what event to listen to in order to execute the actions described in a recipe.|
Trigger events can be set off in apps (e.g. Salesforce, JIRA) when a certain event happens (e.g. new contact is created, existing ticket is updated, when a new line is added in a file, etc.).
Trigger from an app
|2. Run on a schedule||Scheduled triggers are executed at specified days and times, hourly, daily, monthly, etc. At the scheduled time or interval, this trigger will fetch all events matching the specified criteria.|
|3. Trigger from a webhook||Webhooks are notifications sent out by an application to a target URL as soon as an event happens. Typically, you can define specific events you wish to receive notifications for.|
|4. Manage other recipes||The RecipeOps connector enables the building of recipes to monitor and manage active recipes.|
Stopped recipes and failed jobs can have automated responses and notifications to mitigate their impact on critical business processes. Account, recipe and job details can also be retrieved via the RecipeOps connector.
|5. Build callable recipe||Callable recipes are a type of recipe that can be called from other recipes.|
This helps to reduce the length of your recipes by separating a repeatable set of actions into a callable recipe that can be called from other recipes that require the same steps.
A callable recipe is triggered by a call from another recipe instead of a trigger event in an application.
|6. Build an API endpoint||Workato allows for callable recipes to be turned into an API endpoint.|
This means that your callable recipes can be called and used by someone who doesn't need to have access to your Workato account, provided that:
|7. Build slackbot command||Define a Workbot command. When this command is typed in Slack, Workbot will carry out actions in this recipe.|