Working with projects
A project is a container that organizes and manages all the assets that are related to an integration solution. It helps group related assets in a structured way.
The key features of the projects are as follows.
- Isolation - Each project has its own set of integrations, connectors, and configurations, keeping them separate from other projects.
- Collaboration - Teams can work on different projects independently.
- Deployment - Projects can be published and deployed to different environments, for example, development, test, and production. You cannot publish individual integrations.
Common asset types in projects
A project contains various assets that work together to build and run integration solutions. These assets are the building blocks of your integrations, and each serves a specific purpose.
- Integrations
- An integration refers to a process that connects different applications, services, or systems to automate tasks and data exchange. Two types of integrations, workflows and flow services are available. Also, you have recipes, which are pre-built integration templates that help you quickly create integrations.
- APIs
- You can define APIs that enable workflows or flow services to be used externally. For more information, see Creating REST APIs and Creating SOAP APIs.
- Connectors
- Connectors are prebuilt integrations with external applications such as, Salesforce, SAP, or Slack.
- Accounts (Connections)
- Store authentication details for connectors. Each account is tied to a specific service, for example, a Gmail account for Gmail connector.
- Schedules
- Define when an integration runs, for example, every hour, daily. These schedules are for automating recurring tasks.
- Variables and secrets
- Reusable values like API keys, tokens, or environment-specific settings. These assets help manage configurations securely and consistently.
- Reference data
- Reference data is data that defines the set of permissible values to be used by other data fields. It is a collection of key-value pairs, which can be used to determine the value of a data field based on the value of another data field.
- Document types
- A document type contains a set of fields that are used to define the structure and type of data in a document. You can use a document type to specify the input or output parameters for a Flow service.
- Events
- Events are reusable triggers that can be used across multiple workflows within the same project.