Connectors

Connectors link Aleria to the tools your team already uses. Once connected, you can read files, send messages, create events, update tickets, and pull information into Aleria directly from chat and workflows. You do not need to switch between apps to get work done.

What connectors do

A connector is a prebuilt integration to an external system. Aleria talks to that system on your behalf, so the tool becomes both a source it can read and a set of actions it can take while it works.

For example, you can ask Aleria to:

• "Send the weekly summary to #sales on Slack."
• "Find the latest contract in the SharePoint Legal site and summarize it."
• "Add a follow-up task to Trello for the Acme deal."
• "Create a 30-minute meeting with the finance team on Thursday morning."
• "Pull last month's support tickets from Jira and group them by priority."

Available connectors

Your workspace can connect to a range of common business tools. The exact list depends on your deployment, and the up-to-date list is always shown in the Connectors section. Current connectors include:

Microsoft

• Microsoft Outlook
• Microsoft Calendar
• Microsoft OneDrive
• Microsoft Contacts
• Microsoft SharePoint

Google

• Gmail
• Google Calendar
• Google Drive
• Google Docs
• Google Sheets
• Google Slides

Collaboration and project management

• Slack
• Trello
• Jira (Atlassian)
• Confluence (Atlassian)

Development

• GitHub

If you need to bring in a large business system such as a data warehouse or a CRM, that is handled by the data layer rather than by these connectors. See Big Data Fusion.

Connect an account

1. Open the Connectors section in your workspace.
2. Find the connector you want, such as Slack, SharePoint, or Gmail.
3. Choose Connect.
4. Sign in with the account you want to use and authorize Aleria.
5. Choose which sites, channels, or folders Aleria can access, where the tool supports it.

Once connected, the account becomes available in chat and workflows.

Multiple accounts per connector

You can connect more than one account for the same connector. This is useful when you work across personal and work accounts, or when different parts of your organization use separate instances of the same tool.

For example, you might connect:

• Two Outlook accounts, one personal and one work
• Two Google Drive accounts, one for the company and one for a client project
• Two Slack workspaces, one for the company and one for a partner project
• Two SharePoint sites, one for Legal and one for Finance

When Aleria performs an action through a connector, it asks which account to use if you have more than one.

This keeps credentials separated while still letting you reach everything from one chat.

Use connectors in chat

After you connect an account, just ask for what you want in plain English. Aleria knows which connector to use based on your request.

Microsoft examples

• "Send an email to the team with the Q3 summary attached."
• "Find my next three meetings."
• "Get the latest budget spreadsheet from OneDrive."
• "List the files in the SharePoint Legal site."

Google examples

• "Create a Google Doc with the meeting notes."
• "Pull the revenue numbers from the Q2 sheet in Google Drive."
• "Add a reminder to my Google Calendar for Friday."
• "Find emails from Acme Corp from last week."

Collaboration examples

• "Post this report to #general on Slack."
• "Create a Trello card for the website redesign."
• "List open high-priority Jira tickets."
• "Search Confluence for the onboarding playbook."

Use connectors in workflows

Connectors become powerful when you use them inside Workflows. For example:

• Every Monday, pull Jira ticket counts and email a summary to the team.
• When a new contract is reviewed, post the result to a Slack channel.
• After an approval, draft and send a confirmation email.

Permissions and security

Connectors respect the permissions of the account used to connect them. Aleria can only see and do what that account is allowed to see and do in the external tool. If your account cannot open a folder in SharePoint, neither can Aleria.

Administrators can:

• Limit which sites, channels, or folders Aleria can access
• Choose whether a connector is read-only or allowed to take write actions
• Review and disconnect connected accounts at any time

Connectors and air-gapped deployments

Connectors reach out to outside services, so they are not available in fully air-gapped deployments, which by design have no internet connection. In an air-gapped setup, your data comes from sources inside your boundary instead. See Deployment and security.

Troubleshooting

If a connector command does not work:

• Check that the connecting account still has permission for the channel, site, file, or mailbox.
• Confirm the connector is still connected in the Connectors section.
• Make sure you selected the right account, if you have several connected.
• Make sure you are asking for something the connector supports, such as a Slack channel or a SharePoint library Aleria can access.
• Ask Aleria to explain the error. It will usually tell you whether the issue is a permission, a missing access scope, or a naming mismatch.