Understanding Connectors

Connectors let Applied work with the systems your team already uses. They help your AI agent access the right information, keep Data current, and support workflows that need real business context.

What a Connector does

A Connector creates a trusted link between Applied and another system, such as:

A commerce platform like Shopify.
A help desk platform like Zendesk or Gorgias.
A document system like Google Drive or Confluence.
A database or custom API.

Some Connectors are mainly used to bring in reference material. Others are used inside Flows so the agent can look up details or take guided actions.

The three parts to understand

Connectors

This is the connection itself. It tells Applied which external system to use and how to reach it.

Data

Data is the material that comes in through a Connector or another connected source. This can include imported articles, product information, reference documents, or other synced records.

Knowledge

Knowledge is what your AI agent uses to answer customers. Some teams write Knowledge directly. Others connect Data first, then generate or curate Knowledge from that source material.

Common connector categories

The exact list shown in your workspace may differ, but common categories include:

Commerce for store, billing, and subscription systems.
Support for help desk platforms.
Productivity for documents, notes, and shared knowledge.
Databases for structured business data.
Messaging for internal team communication.
Content for site, docs, and blog sources.

How Connectors fit into Applied

Connectors usually support one or more of these workflows:

Bring external material into Data.
Help you create or improve Knowledge.
Provide lookup or action steps inside Flows.
Give human agents better context during escalations.

For example, a team might sync product information into Data, connect it to Knowledge, test it, then use a Flow to look up order details during live conversations.

When to use a Connector

Use a Connector when:

Important information already lives in another system.
Your team wants updates to stay in sync over time.
A Flow needs to fetch or update real-world information.
You want fewer manual copy-paste steps between tools.

Write Knowledge directly when:

The answer is short and stable.
You want precise wording that should not be generated from source material.
The content changes rarely and is easier to manage inside Applied.

What sync means

Sync keeps your Data aligned with the source system.

Depending on the Connector, you may be able to:

Run a manual sync when something important changes.
Set a regular sync schedule.
Review when a source was last refreshed.
Regenerate Knowledge from updated Data.

Syncing Data does not mean every customer answer should be automatic. Your team should still review high-impact material and test changes before relying on it in production.

A simple setup path

Connect the external system in Connectors.
Review the imported or synced material in Data.
Turn the right material into Knowledge.
Test your agent and any related Flows.
Monitor performance and resync when the source changes.

Best practices

Start with one high-value source before connecting everything.
Keep source material clean, current, and easy to understand.
Avoid importing duplicate material from multiple places.
Use Data for reference material and Knowledge for the final answer behavior.
Re-test after major source updates.