Skip to main content

First Party Connector Documentation

First‑Party Connectors in ChatLLM Teams let you connect Abacus.AI to multiple data sources so that:

  • you can query connected sources directly via prompts.
  • all Chatbots and Abacus AI Agent in your workspace can freely query data from these connectors once the connection is set up.

Available Connectors​

  • Slack
  • Teams
  • Confluence
  • Jira
  • Sharepoint
  • Gmail
  • Google Drive
  • Google Calander
  • Onedrive
  • Box
  • Github
  • X
  • Outlook
  • Autodesk
  • Reddit
  • Dropbox
  • Smartsheet
  • HubSpot
  • AWS SSO
  • DocuSign
  • Tableau
  • NetSuite
  • Zoom (coming soon)

Creating and Using a First Party Connector with RouteLLM​

This section walks you through creating a first party connector and then using it directly in chat with RouteLLM — Abacus.AI's automatic model router. The steps below use Zoom as the example, but the same flow applies to any first party connector in the list above.

Step 1 — Open the First Party Connectors panel​

In ChatLLM Teams, click the Connectors link on the home page, or click your profile in the top right and navigate to Profile → First Party Connectors.

Add Connectors panel listing available first party connectors

Step 2 — Select and connect the service​

  1. Scroll the connector list and click on the service you want to connect (for example, Zoom).
  2. A browser pop-up opens asking you to sign in to the service and authorize Abacus.AI.
  3. Review the requested permissions and click Allow (or Authorize).
  4. After authorization completes, the connector appears under your connected services and is ready to use.
info

First party connectors are configured once per user and run under your own identity. After the connector is set up, every chatbot and the Abacus AI Agent in your workspace can query data from it.

Step 3 — Start a chat with RouteLLM​

  1. Open a new chat in ChatLLM Teams.
  2. From the model selector, choose RouteLLM (route-llm). RouteLLM automatically routes each request to the most suitable underlying model, and is available for unlimited use to ChatLLM subscribers.
Selecting RouteLLM from the chat model selector

Step 4 — Query your connected data​

Ask a question that references the connected service, for example "List my Zoom meetings scheduled for this week". RouteLLM will invoke the connector's tool, fetch the data under your identity, and respond in chat.

The first time you query a newly connected service in a chat, you may be prompted to authorize the connector. Complete the sign-in once and the request continues automatically; subsequent requests reuse the connection.

tip

You don't need to train a Custom Chatbot to use a first party connector with RouteLLM. Once the connector is configured in the First Party Connectors panel, it is immediately available across your workspace chats.

Customization options using config connectors​

Sharepoint​

Configuring SharePoint Connector Permissions

By default, the SharePoint first-party connector is provisioned with read-only access to ensure data security. If your workflow requires the ability to create, modify, or delete files and folders, you must explicitly enable read and write capabilities.

To upgrade your SharePoint connector from read-only to read-write access, please follow these steps:

  1. Navigate and Turn Config Only toogle ON:
  • Go to the Abacus.AI Connected Services Dashboard. You can click your profile in the top right and then click "Manage Connectors".
  • Click on the "Add New Connector" option, select "SharePoint" from the list, and turn "Config Only" toggle on.
Config Only
  1. Select Authentication Type:
  • Select "Basic" if you want to use Abacus.AI app for read only Sharepoint user connector.
  • Select "Write" if you want to use Abacus.AI app for read and write Sharepoint user connector.
  • Select "Custom Auth" if you want to use your own app with Sharepoint User connector.
Config Only Authentication
  1. Enter credentials:
  • Enter Sharepoint site URL
  • Enter client ID and secret if you have selected "Custom Auth".

Navigate back to ChatLLM and create a Sharepoint first party connector with read-write access.

Outlook​

By default, the Outlook first-party connector is provisioned with read-only access to maintain a secure environment for your communications. If your workflow requires the ability to send emails, or create calendar events, you must explicitly select required scopes.

To upgrade your Outlook connector from read-only to read-write access, please follow these steps:

  1. Go to the Abacus.AI Connected Services Dashboard. You can click your profile in the top right.
  2. Select "Manage Connectors" from the dropdown menu.
  3. Click on "Add New Connector", choose "Outlook" from the list.
  4. Turn the 'Config Only' toggle on.
  5. Select the appropriate scopes to grant us the necessary access.
  6. Click create.

Navigate back to ChatLLM and create a Outlook first party connector with read-write access.

Tableau​

The Tableau first-party connector is a zero-interaction connector that reads Tableau Cloud content (workbooks, views, published data sources, and projects). It requires an org-level config connector that stores your Tableau Connected App (Direct Trust) credentials — there is no per-user OAuth/login pop-up; the signed-in user's email is used to connect.

To set up the Tableau config connector:

  1. In Tableau Cloud (as a site admin), create a Connected App (Direct Trust) under Settings → Connected Apps, enable it, and generate a secret. Note the Client ID, Secret ID, and Secret Value.
  2. Go to the Abacus.AI Connected Services Dashboard and click "Add New Connector", then choose "Tableau".
  3. Turn the Config Only toggle on.
  4. Enter the Tableau Server URL, optional Site Content URL (leave blank for the default site), and the Connected App Client ID, Secret ID, and Secret Value.
  5. Click Create.

A matching Tableau user (same email as the Abacus.AI account) must exist on the Tableau site for end users to connect. For the full walkthrough — including using the Tableau tool in a chatbot — see the Tableau User Connector Setup Guide.

NetSuite​

The NetSuite first-party connector reads and writes NetSuite data through the SuiteTalk REST Web Services API. It requires a config connector that stores the credentials of an Integration Record (OAuth 2.0 application) created inside your own NetSuite account. Each end user then signs in to NetSuite through a normal OAuth pop-up, so the agent runs under that user's own NetSuite role.

To set up the NetSuite config connector:

  1. In NetSuite (as an administrator), enable REST WEB SERVICES and OAUTH 2.0 under Setup → Company → Enable Features → SuiteCloud.
  2. Create an Integration Record under Setup → Integration → Manage Integrations → New with AUTHORIZATION CODE GRANT checked, the REST WEB SERVICES scope selected, and the redirect URI https://abacus.ai/oauth/callback. Copy the Client ID (Consumer Key) and Client Secret (Consumer Secret) — NetSuite shows them only once.
  3. Grant the Log in using OAuth 2.0 Access Tokens, OAuth 2.0 Authorized Applications Management and REST Web Services permissions (Level Full) to the role your users will use, and assign that role to them.
  4. Go to the Abacus.AI Connected Services Dashboard, click "Add New Connector" and choose "NetSuite".
  5. Enter the Account ID, Client ID (Consumer Key), Client Secret (Consumer Secret) and Scopes (rest_webservices is required), then click Create. The NetSuite config connector is inherently config-only, so there is no "Config Only" toggle to turn on.

For the full walkthrough — the administrator setup, the end-user sign-in flow, and using the NetSuite tool in a chatbot — see the NetSuite Connector Setup Guide.