Integration Studio concepts

Before you look at use cases, here are the concepts you will encounter:

• Project: a group of automations, which makes them easier to manage and to share with your team. Each project can contain several recipes (workflows).
• Recipe: an automated workflow that runs a series of steps to integrate and process data across several applications. For example: "when a case is approved in Dotfile, create a record in Salesforce and send a message to Slack." Recipes are built in a no-code designer and can connect several apps.
• Connection: a secure authorization that lets recipes access one of your apps, such as Dotfile, Slack, Salesforce or HubSpot. Connections are reusable and managed centrally in Integration Studio.
• Trigger: every recipe begins with a trigger, the event that sets the workflow running. Triggers can be:
  • Polling: checks regularly for new data or changes.
  • Real-time: responds instantly to events, often through webhooks.
  • Scheduled: runs at set times or intervals.
  • Change Data Capture (CDC): detects and acts on database changes.
• Steps and actions: a recipe runs its steps each time a trigger event occurs. Every recipe needs at least one step. The simplest step is an action, such as fetching results from webhooks, fetching company data, creating an individual, sending a Slack message or updating a HubSpot contact.
• Job: one trigger event traveling through the recipe. A job succeeds when every action succeeds. If an error occurs, the remaining actions do not run unless error handling is configured.
• Task: each action a recipe runs counts as a task. Task usage is tracked and can be monitored in your dashboard.

📖 Learn more: Recipes documentation.