What is a Recipe?

A Recipe is we call workflows in our Custom Integrations! With a recipe, you can determine how you want your workflow to be set up.

Drew Wilkinson avatar
Written by Drew Wilkinson
Updated over a week ago

πŸ“Œ Note: This article refers to our Custom Integrations which are available to users on all plans as an add-on service.

A Recipe is basically what we call workflows in our Custom Integrations feature! With a recipe, you can determine how you want your workflow to be set up, when you want to execute it, and use conditions to perform different tasks for different objects.

To get a better understanding of how recipes work, let's take a look at the various components of a standard recipe page:

​A Recipe has page has the following components:

  1. Unique Recipe ID - This can be found in the URL as shown above

  2. Name - This is the Name that you set for your recipe, in order to easily identify it in your library

  3. Copy and Delete Buttons - Allows you to clone your recipe or delete it

  4. Job Completion Overview - Allows you to see at a glance how many jobs has the recipe successfully and unsuccessfully processed

  5. Jobs - allows you to track each individual job that has been processed by the recipe, and also aids you in determining the causes of recipe errors

  6. Connections - Allows you to see which app account you are using for this particular recipe

  7. Versions - This allows you to keep track and reset to a previous version

  8. Trigger - This is what starts off the recipe, ie when a certain task in performed in an app, start this recipe

  9. Actions - The set of steps that are performed after a recipe is triggered

Did this answer your question?