The platform in practice
Integrations and actions
Connected accounts, available tools, and controlled execution of actions in connected systems.
An integration consists of a connected account and a set of explicitly available tools. An organization can connect several accounts from the same provider, and tools can be enabled separately for each account. The selected assistant can narrow the available set further.
Available integrations
Slimaco connects to the suites companies work in every day: Microsoft 365 (Outlook Mail, Outlook Calendar, OneDrive) and Google Workspace (Gmail, Google Calendar, Google Drive).
On top of that, the platform uses the Composio integration layer, which gives access to 1,000+ apps: CRM systems (e.g. HubSpot, Pipedrive, Salesforce), messaging (Slack, Microsoft Teams, Zoom), project tools (Jira, Asana, Notion, Trello), finance and accounting, e-commerce, HR and many more. See the full list on the Integrations list page.
Connected department systems such as CRM, ERP, helpdesk, invoicing, Slack and Microsoft Teams also feed shared company knowledge. Agreements and decisions go through review, while hard data, such as the number of a customer's open tickets, updates continuously. More on the Organizational knowledge page.
Each integration is connected with an organization account, and its tools are enabled separately. Agents created by the Slimaco assistant can use connected apps on demand or on a schedule, always within the permissions and consent rules described below.
Read and write
| Action type | Example | Control |
|---|---|---|
| Read | Finding a file, message or event | Plan, role, tool and account must all be available |
| Preparing an artifact | A draft answer or document | The result stays with the user for review |
| A write behind the write guard | Creating a draft message, file or event | The Slimaco assistant pauses and shows a consent card |
| One-time or time-boxed consent | Once only, for the conversation, or up to 30 days | Consent is tied to the tool, user, account and scope |
| Refusal or error | The user declines, or execution isn't confirmed | The action is never presented as done |
What action consent looks like
The Slimaco assistant shows a card with the action's name, service, account and parameters. The user can allow it once, for the conversation, on a time-boxed basis (up to 30 days), or decline. Drafting, saving to a mailbox and sending are separate actions and each requires its own tools and policies — Slimaco does not send a message without explicit consent for that specific step.
Multiple accounts from one provider
Slimaco supports multiple accounts from the same provider at once. Picking a specific account directly inside a conversation isn't yet a universal selector — when several accounts conflict, a tool setting may need to be changed in the Integrations panel.