Connectors & destinations
A connector links a workspace to an external system for input and output. Today that system is Google Drive. Every pipeline also always exposes its result over the Web Response API, whether or not a connector is attached.
A connector is a workspace-level link to an external system. It can act as a source — documents that arrive there are fed into a pipeline — and as a destination — the pipeline's results are written back to it. Connectors are managed in Settings → Integrations, separately from any one pipeline, so the same connector can serve whichever pipeline binds to it.
Google Drive, today
The only connector type today is Google Drive. A Google Drive connector watches one input folder and writes to one output folder, and it feeds one published pipeline. A file dropped into the input folder is processed by that pipeline; the result is written to the output folder when the job completes.
A Google Drive connector on the Connectors tab, showing its input and output folders and its last poll. One connector, one Drive account, one pipeline.
Web Response is always on
Independently of any connector, every pipeline ends in a Destination stage whose Web Response output is always on. The result of every job is retrievable over the Job Results API and visible in the API Playground — a connector adds a delivery target, it never replaces the API. A pipeline with no connector still returns its result; it simply has no external folder to write to.
The Destination stage
The Destination stage decides where a finished result goes. It carries two things: the always-on Web Response, and any Deliver to Google Drive targets bound from the workspace's connectors. The output format — for example JSON — is set on the Post Processing stage, not here; the Destination stage governs routing, not shape.
Delivery semantics
- On completion — a connector receives the result when the job finishes, not while it is still processing.
- Test runs do not deliver — a run submitted in test mode returns its result over Web Response but is never written to a connector's output folder, so trying a pipeline never touches a live Drive folder.
- One pipeline per connector — a connector feeds a single published pipeline, which keeps a document's route unambiguous.
What exists today
| Connector | Input | Output |
|---|---|---|
| Google Drive | Watches one Drive folder | Writes results to one Drive folder |
Other connector types are not yet available. Until then, endpoints that need the result programmatically use the Web Response API, and outbound notifications use webhooks.