# Core Components

The following table lists core components of DBSync's platform. These components are related to the ETL concepts to help readers attain an in-depth understanding of how the whole platform works.

<table><thead><tr><th width="224">Component</th><th>Description</th></tr></thead><tbody><tr><td>Project</td><td>A <strong>Project</strong> is the top-level container that encapsulates everything required to solve a business integration requirement. It includes a set of <strong>Connectors</strong>, <strong>Tasks</strong>, <strong>Flows,</strong> and <strong>Mappings</strong> that work together to move and transform data between systems. Projects organize integrations in a modular and reusable manner.</td></tr><tr><td>Automation</td><td>Automation is a combination of control flow and data flow that together define the complete integration logic for a specific process. It includes configurations, execution rules, and error-handling logic. A single project can contain multiple automated tasks, each targeting different workflows. It enables automated integrations for efficient data management. Learn more.</td></tr><tr><td>Task</td><td>Task allows you to create and assign processes to any agent in your team.</td></tr><tr><td>Flow</td><td>A <strong>Flow</strong> in DBSync represents a specific automation or workflow you want to execute. It uses queries, variables, and logic to drive data processing and transformation. Each flow can be independently enabled or disabled, controlling whether that workflow runs during integration execution. Learn more.</td></tr><tr><td>Connectors </td><td><strong>Connectors</strong> are configuration components that handle authentication and connection setup to external systems or databases. They store connection parameters (like URL, tokens, keys, etc.) required to establish a secure link between DBSync and the endpoint. Each connector is linked to an App to define the type of data interaction. They support both pulling data from and pushing data to target systems by leveraging APIs, JDBC/ODBC, or file protocols. Learn more.</td></tr><tr><td>Actions</td><td><strong>Actions</strong> are the smallest executable units within a Flow in DBSync. They define what operation to perform on data—such as reading, writing, transforming, or even applying conditions. Each action interacts with a specific system (via the configured connector and app) and executes a defined function like querying data, inserting records, or looping through results. For example, query, transform &#x26; write, if, for, storage actions, and others. Learn more.</td></tr><tr><td>Template Library</td><td>Contains pre-defined projects with default mappings for integrating applications such as Salesforce and QuickBooks etc. Learn more.</td></tr><tr><td>Forms</td><td><p><strong>Forms</strong> in DBSync are user-friendly interfaces designed to simplify the setup of integration projects. Instead of configuring every detail manually, developers can create customized forms that ask a series of questions. Learn more.</p><p>These forms act as a guided setup wizard, allowing users to input values that are automatically injected into the underlying configuration (like queries, mappings, and connectors). Learn more.</p></td></tr><tr><td>Scheduler</td><td>The <strong>Scheduler</strong> allows you to automate the execution of Tasks at predefined intervals—daily, weekly, hourly, or even custom CRON expressions. It ensures that your integrations run without manual intervention, making it a key component for continuous data sync between systems. Learn more.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mydbsync.com/cloud-workflow/2026_getting-started/core-components.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.