Skip to content

Platform · Integrations

Connect the AI to the systems your company already uses.

Spreadsheets, email, CRM, projects, support: Skyller reads from and acts in those systems through the functions your company enabled, with each person's own login and confirmation before sensitive actions. Below, the catalog updated from the vendors: search by name or by what you need to do, filter by category or country, and open each integration to see the available actions and what it takes to start.

Try it freeBook a demo
See the catalog
Skyller · Sources and tools

Conversation sources and tools

A lookup in the source selected for this conversation.

Skyller
Read-only lookup
Where is the onboarding meeting summary?
Google DriveIllustrative configuration
Lookup function
Find file

Find file

Demonstration · illustrative data

669 CONNECTORS

in the catalog · September 2026 list

21 CATEGORIES

from spreadsheets and email to CRM, projects and support

FUNCTION BY FUNCTION

the company enables only the actions each team needs

EACH PERSON'S LOGIN

own credential, encrypted; not even the admin sees it

Where this helps your work

Three requests that end today with another tab open.

The system has the information; the person needs it in the conversation they are working in. The integration brings the AI to the system — within what the company enabled.

Closing the month

“Pull September's receipts from the spreadsheet and compare them with the policy.”

The analyst asks in the Finance hub. Skyller reads the spreadsheet through the Google Sheets connection, checks it against the published collection policy and returns the discrepancies — nobody copies a cell.

System data in the answer

Preparing the meeting

“Summarize this customer's history in the CRM before the call.”

The salesperson asks by customer name. Skyller queries the connected CRM — HubSpot, Pipedrive or Salesforce, when enabled — only through the read functions enabled for the sales team, and builds the summary with the latest interactions.

CRM context in the conversation

Handling support

“Open a ticket with what the customer reported.”

The agent asks to log the ticket. Because creating a record is a write action, Skyller shows a card with what it is about to create and waits for approval before touching the support system.

Action with approval and record

How it works

Choose a connector, connect the account and authorize actions.

The catalog shows what the vendor offers. From there, your company decides what the AI can do — and Skyller records every call.

  1. 01

    Pick from the catalog

    Search for the system by name or by what you need to do. Each integration shows the actions and events the vendor makes available, the login type and the category.

  2. 02

    Connect

    An administrator installs the company connection; a person can connect just for themselves and try it. When the system requires a login, each person signs in with their own account — the credential is stored encrypted.

  3. 03

    Enable function by function

    Out of dozens of actions in a system, the administrator turns on only the ones the team needs. Every action has a risk level, and sensitive ones start asking for confirmation.

  4. 04

    Ask as usual

    Nobody picks a tool. The person asks in the conversation; Skyller selects, among the functions available and allowed for them, the ones that solve the request.

  5. 05

    Act with approval and a record

    Reading happens directly. Creating, changing or sending shows a card with what is about to happen and waits for Approve. Who asked, what was done and when are recorded.

What you need to know

Nine things that change what you can promise your team.

Select a topic to see its capabilities, conditions, and limits.

Catalog updated from the vendors
Integrations and their actions come from the vendors' catalogs and are synchronized periodically. What the vendor drops stops being offered; the last valid version of the catalog stays published.
Curated by Skyller
Not everything a vendor lists shows up here: Skyller publishes a selection, with a purpose in plain language and a country when it matters. Your company can still hide integrations from its own catalog.
The company's own systems
ERP, legacy system or internal portal come in through a standardized bridge that exposes only the chosen functions, registered by the company with an address, headers and a connection test. Internal-network connections can go through the desktop app.

Live proof

Two out of fifty functions. And the same question does not run the same for everyone.

It is the argument IT gets instantly: opening the whole system to use two functions is needless risk. In Skyller, permission applies to the agent and to the person who asked.

  1. Input

    The administrator connects the company's finance system and, out of the connector's dozens of actions, enables only Look up order and Record payment for the finance agent.

  2. What Skyller does

    1. 01Ana, from Finance, asks about order 4821: Skyller looks it up and answers right away — a read does not open a card.
    2. 02Ana asks to record the payment: Skyller shows the card with order, amount and date, and only runs it after Approve.
    3. 03Bruno, from Sales, asks for the same payment record: the function is outside his role. Skyller looks up the order but records nothing.

  3. Result

    Two functions enabled, one human approval and a record of who asked for what — the rest of the system stays closed.

What this scene does not promise

  • Each action's risk level has an initial classification the company can adjust; what asks for confirmation is the company's decision, not a fixed rule for every system.
  • Corporate systems that are not in the catalog come in through a bridge of their own, built by IT, the vendor or a partner — or by Skyller as a separate service.
  • Having the integration in the catalog is not the same as having it installed, with a valid login, working in your company.

Illustrative scene with fictitious data; the permission and approval mechanism is the product's.

Real application

From the catalog to the first approved action, in one afternoon.

The path an administrator and an analyst take to bring the collection spreadsheet into the conversation — with what depends on configuration made explicit.

  1. 01Administrator

    Searches “spreadsheet” in the catalog, opens Google Sheets, reads the actions and installs the company connection.

    Installing for the company is an administrator's job; the number of company connections depends on the plan.

  2. 02Finance analyst

    Signs in to her own Google account when the conversation asks; the credential is stored for her only.

    A system with a login requires each person's account; nobody shares a password.

  3. 03Administrator

    Turns on only “read range” and “find row” for the finance agent; leaves “delete spreadsheet” off.

    The enabled actions depend on what the vendor exposes and what the company decides.

  4. 04Finance analyst

    Asks “which September customers have overdue invoices?” and gets the list read from the spreadsheet, with the rule from the collection policy.

    Skyller picked the read action on its own; the policy comes in because it is published.

  5. 05Skyller

    On the request “log the pending collection on the team board”, shows the task card and creates it only after Approve.

    Creating on the board is a sensitive action: it goes through approval and is recorded.

Comes ready

  • Catalog synchronized with the vendors, with search, categories and a detail page per integration
  • Installation from the Plugins screen, each person's login and encrypted credential
  • Initial risk classification per action and an approval card for sensitive actions
  • Automatic selection of the right tool and a record per call

The company decides

  • Which integrations are visible in the company catalog and which connections exist
  • Which functions of each connection are on, and for which groups
  • Which actions ask for confirmation and who can approve
  • Whether a proprietary system comes in through a bridge built by IT, the vendor, a partner or Skyller as a service

Questions from the people who decide

What usually stalls the decision.

Next step

Bring the system your team uses the most.

Try it free with your team or book a demo with one of your connections: from the catalog to the first approved action, with fictitious data and the functions you choose.

Try it freeBook a demo