Skip to main content
Integrations allow your Agent to connect directly with third-party applications and services. An Integration either brings documents into an Agent or sends its results out:
  • Input: documents coming into the Agent
  • Output: results going out of the Agent
See the full list of all supported integrations here and steps on how to integrate with them. Agents can also be connected using our API or Python Client.

​
Configuring Integrations

Integrations are configured for each Agent from the Workflow graph on the main Agent page. The Workflow graph starts at an Input node and ends at an Output node, with the Agent’s Prompts in between. Each node lists what is currently connected to it. Clicking a node opens a panel where you can manage it:
  • From the Input node, click “Upload Files” to add documents yourself, or “Import from Integration” to bring them in automatically.
  • From the Output node, click “Add Output Template” to shape the results, or “Send to Integration” to send them somewhere.
On a large Agent, use the “Jump to” control above the graph to bring the Input or Output node back into view. An Integration you connect is available to every Agent in the Workspace, and sharing one lets other people attach it to their own Agents. To view your integrations, open your user profile at the bottom of the sidebar, click “Profile Settings”, then switch to the “Integrations” tab. Administrators, and anyone with a Custom Role granting the “View Integration” action, can see every Integration connected across the Organization from the “Integrations” tab on the Organization page.

​
How Integrations Work

​
Input Integrations

If documents come in from a file storage system (e.g. Box, Google Drive, S3), the Agent will automatically watch it for new files. When new files are detected, the Agent will create new Runs to process those files. See Cloud Folder Sync for details on how folders are kept in sync. An Input Integration can read files in two different patterns:
  1. Import Files Separately: Each file in the connected location is processed as a separate Run.
  2. Group Files Together: All files in a sub-folder pattern are processed together, where each sub-folder’s content as a single run by the Agent.

​
Output Integrations

If results go out to a file storage system (e.g. Box, Google Drive, S3), the Agent will write output files to it after each Run is completed. An Output Integration can write files in two different patterns:
  1. Write to Directory: Each Run by the Agent produces output files sent to the Integration.
  2. Write to File: Each Run by the Agent produces a row in a single output spreadsheet.
You can send your results to an Integration as PDF, Word, Excel, CSV, JSON, or Powerpoints. You can also use templates to customize the format of your output files.

​
Example Workflows

These patterns can be combined. Let’s consider how to model some example workflows:

​
Lease Abstraction

Suppose you have multiple lease documents and amendments for various properties stored in a Box.com folder:
and you want to generate an abstract file for each property.In this case, you would bring documents in from the Box.com folder, grouping files by subfolder (i.e., Property_A, Property_B) so that each property’s documents are processed as a single run. The output can then be sent to another Box.com folder, with one output file per run.

​
Utility Bill Extraction

Suppose you have a folder of utility bills in Google Drive which you want to extract key details into a table, which one row per bill:
In this case, you would bring documents in from the Google Drive folder and send results out to a single Google Sheet. The output of each runs will be synced to a new row in the Google Sheet.

​
FAQ

​
I’ve connected an Integration, when will my Agent start processing files?

Files already in the connected location are imported when the Integration is added, and new files are typically detected within a minute or two of being added. For Integrations that group files together, Kolena waits until a sub-folder has been quiet for 5 minutes before processing it, so it may take up to five minutes before new runs are created. When connecting a folder that already contains a large number of files, the initial import happens in batches and may take some time to complete. See Cloud Folder Sync for details.

​
How many Integrations can I add to my Agent?

A single Agent can have multiple Integrations bringing documents in and sending results out.

​
What happens if I add a new file to a connected folder?

For Integrations where files are imported separately:
  • If a new file is added, Kolena will create a new run for that file
For Integrations where files are grouped together:
  • If a new file is added to a sub-folder, Kolena will create a new run if one does not exist or update an existing run if one already exists for that grouping.

​
What happens if I remove a file from a connected folder?

By default, Kolena will not delete or update existing runs if a file is removed. Grouped folder Integrations on Box, Google Drive, and SharePoint can opt in to syncing deletions, which removes deleted files from their Runs and either re-runs the affected Runs or marks them as stale.

​
What happens if I move a file into or within a connected folder?

A file moved or copied into a synced folder is imported the same as a new file, even if the file itself is old. For files moved between sub-folders within a synced folder, the file is imported at its new location; the copy at the old location is only removed if syncing deletions is enabled.

​
What happens if I delete a Run or file in Kolena?

The deletion is permanent: syncing will not re-import the file from the same location, even during a full re-scan. If the file later appears in a different location, it is treated as new and imported there.

​
What happens if I update a file in a connected folder?

If you update the content of an existing file, Kolena will not automatically re-process the updated files or refresh existing runs.