There are over 200 hundred pre-built application and technology connectors, developer tools and workflow templates included within the Flowgear platform, across various software categories (eg. ERP, CRM, Accounting).
Flowgear workflows are composed of a series of Application and Technology Connectors that enables communication between two or more systems or applications, allowing them to exchange data and perform actions with each other.
Our connectors provide a wrapper around a third party service or data source and are designed to abstract away the complexities of connecting to and working directly with a 3rd party APIs, by visually surfacing all the available functions and attributes.
For products that do not have an API, technology connectors provide access to common standards for databases, file systems and transports.
All core connectors are constantly refreshed by the Flowgear technical teams to match the latest vendor product releases.Connectors can also be used to enable a variety of different types of communication between systems or applications, including the exchange of data, the triggering of actions, and the integration of different systems or applications. Some connectors are designed to be used by developers, while others are more user-friendly and can be used by non-technical users.
Developers are able to easily build their own connectors using the Flowgear software development kit (SDK).
What are you trying to connect?
Where there is a need for industry vertical or highly specialized connectors that are not part of the Flowgear toolbox, developers can build their own connectors with very high ease of use. The test harness implementation allows developers to place connectors that are under development onto the live design canvas and then live-debug them from within their development environment as they are invoked from the Flowgear engine. This approach drastically compresses time and reduces complexity of building connectors.
Flowgear enables the option for citizen integrators, the term for business users with some technical knowledge who can perform certain operations. Citizen integrators can compose trigger-action workflows by re-using lower level workflows that have been published by developers. This allows citizen integrators to use existing workflows for other practical applications without always relying on the development team. The resulting solutions provide high ease of use, without compromising security and control.