Skip to main content

Tenovos Connect Getting Started

Tenovos Connect is an integration platform that allows you to build, automate, and scale enterprise workflows with a no-code drag and drop experience. It also includes an application connector for Tenovos DAM that always uses the latest version of the Tenovos API for all connections to Tenovos.

Whether you’re looking to send out a Slack notification any time an asset in Tenovos is deleted, or you’re looking for a fully integrated Product Information Management (PIM) to Tenovos DAM solution or to keep your storefront up-to-date, your Recipe can be up and running within minutes.

As an enterprise integration platform, Tenovos Connect can quickly solve automation needs such as multi-channel distribution, metadata enrichment with the Artificial Intelligence (AI) system of your choice, e-commerce publication and synchronization, and more.

Tenovos Connect Terminology​

This section introduces Tenovos Connect terminology essential for understanding how Recipes function. After you familiarize yourself with the terminology outlined in this section, you’ll be ready to create your first recipe!

Trigger​

A Trigger is the event that determines when your Recipe will run. For example, adding a file to Box might be the Trigger that initiates a Recipe that results in creating a new asset in Tenovos. In this case, until a file is added to Box the Recipe will not run.

Real Time Trigger: Triggers that operate in “real-time” use webhooks to be notified that an event has occurred. If that event meets your criteria, your Recipe will run. Most third party systems offer several pre-built Real Time Triggers to choose from.

Polling Trigger: Triggers that request data from a third party system on a schedule, i.e., every 5 minutes, are called Polling Triggers. These Triggers make an API request to the third party system to determine if anything new is available and therefore should be processed.

Action​

Actions are run once the Trigger’s criteria is met. You can think of Actions as the blocks in a workflow diagram. Actions represent the steps to be performed. Each Recipe can include multiple Actions, such as create an asset, search for assets, download an asset, create a user, generate a translation, etc. Specific business logic such as parsing text, performing calculations and data manipulation are also considered Actions. Recipes can contain as few as one, or as many as needed to accomplish the goal of the Recipe.

Recipe​

A Recipe is a set of instructions that automates a business workflow. Each Recipe is made up of a single Trigger that initiates the Recipe and one or more Actions that are carried out when the Trigger’s criteria is met.

Recipes contain all the API connections (also known as “Connectors”) and business logic for your integration use case, as well as error handling and retry logic. It serves as detailed documentation for your integration and always reflects the current state.

When naming your Recipes, it’s important to be explicit about what the Recipe does. For example, a good descriptive Recipe name could be, “Create Tenovos assets in real time when files are added to Box folder.” This name makes it clear what systems are being integrated (Tenovos and Box) as well as the Trigger type (real time) and the goal (create Tenovos assets).

Connector​

A Connector is a pre-built integration that exposes an application's functionality via their own API—for example, Google Drive—from which you can download content and use it to create assets directly in Tenovos, via the Tenovos API. A Recipe requires at least one connector (application) and often includes more than one. When building out a Recipe, recently used/already connected Connectors are listed under the “Apps” tab. If the Connector you are looking for is not visible, you can search for it when choosing the App for your recipe Trigger or Action.

Examples of Apps/Connectors are: Tenovos, OneDrive, Box, AirTable, Salesforce Marketing Cloud, Jira, Salsify, Bluestone, SharePoint, Gmail, etc.

Connection​

A Connection is required to authenticate to each Connector. These Connections are built into the Connectors themselves and therefore entirely leverage the native authentication of that third party system, i.e., Box.

In order to create a Connection within any Connector, you’ll need valid credentials and/or a valid API key for that system.

RECIPE RECAP

  • A Recipe contains every piece needed for the integration as a whole.
  • In order to build a Recipe, you’ll start by creating a Connection (authenticate) to the Connectors (third party systems) your Recipe needs to use.
  • Every Recipe must have a Trigger which defines some criteria to determine whether or not the Actions in the Recipe should be run.
  • The Actions in the Recipe act as the workers, the steps that fulfill your workflow. This includes writing to logs, making API calls, etc.

Connection(s) → Connector(s) → Trigger → Action(s) = Recipe

Task​

A Task is a billable Action that occurs when a Connector or “App” is used in a Recipe. In general, all successfully run Actions are counted as Tasks and failed Actions are not counted.

Error handling, conditional logic, and other Actions that do not make use of an “App” do not count as Tasks and are therefore not billable.

Your Tenovos Connect plan includes a specific number of Tasks. Customers can purchase additional Tasks at any point by contacting Tenovos Customer Success.

Job​

A Job is a completed execution of a Recipe from its beginning Trigger event to the completion of all specified Actions. Jobs can be successful or encounter errors and fail. Jobs are accessible from the UI and can be retried if needed. Within a job, you can inspect the Recipe to see what data passed through the Trigger and each Action, as well as access all the debug logs for advanced troubleshooting.