If you are here is because you are a Vendor or Provider and you want to integrate Connect to your system. Excellent!! With Flowgear you will make your integration in minutes!!
With Flowgear you build one or more workflows with which you will automate your process end to end. Everyone these workflows are built by nodes of Flowgear connectors.
A Flowgear workflow is an automated integration that connects your apps and services together. Every workflow consists of a trigger step (“when this happens…”) and one or more action steps (“then do this…”). When you turn your integration on, it will run the action steps every time the trigger event occurs.
There are two ways you can create integrations: with a Flowgear template or from scratch.
You can find pre-built or shared workflows to start your integration. (more info in this link)
You can also create your Workflow from scratch. Go to Workflows and select the + icon. then a canvas will open. This canvas has only one “Start” node. This node is the start point of the integration. You must select and place nodes and connections to build the workflow.
Before plan your workflow you must know a few concepts about Flowgear
In Flowgear, workflows are used to describe an integration visually.
All objects in the Workflow are added to the design canvas. You can move around the design canvas by dragging it and zoom in or out using the mouse scroll wheel.
Nodes are the building blocks of a Workflow. Build an integration by adding a series of Nodes and connecting them together with Flow Connectors
▽on the Node Header
There are two kinds of Flow Connectors – Execution Flow Connectors and Data Flow Connectors.
Execution Flow Connectors govern the sequence of execution of Nodes and usually connect between Node Headers (the exceptions to this are the Start Node and Nodes that have multiple Execution Outputs like If or Choose).
Data Flow Connectors control how data moves between Nodes. They connect between properties on Nodes.
A Connection represents an endpoint for a data source. Connections are stored per Site and are accessed from the Connections Pane within the Console. Connections are created against a specific Node and typically include properties for an endpoint and credentials (although they may include other types of properties as well).