Product
Connect any system, no code required
Build your REST integrations without writing code, handle every authentication mode and reuse a ready-made catalog.
KIOP
New conversation
Monitoring
Dashboards
Conversations
Data and knowledge
Data tables
Document library
Orchestration engine
Integrations & API
Workflows
Settings
Users and groups
AI provider settings
AI answers
Usage and quotas
Log and audit trail
Orchestration engineIntegrations & APIConnect a service en Claire MorelCM
Back
Pick a ready-made service: its actions and URL are already written, you only give your credentials.
Search for a service
You set everything up yourself: the URL, the actions and the access. It takes longer, and it works with any API.
Gmail, for the connected Google account: search the mailbox, read a message and its attachments, send one.
5 ready actionsGoogle Sheets: read a sheet’s rows, add some, change one.
6 ready actionsAtlassian Jira Cloud: search tickets, read one, create one, and comment on a ticket.
4 ready actionsMailerLite: add or update a subscriber, put them in groups, find a subscriber.
3 ready actionsPerfex CRM: find or create a company and a contact, open a support ticket.
5 ready actionsServiceNow: service desk incidents (read, open, comment, close), requests and assets.
20 ready actionsYour integrations become tools for the AI assistant
Connect once, then just ask: the AI assistant can call your integrations as tools.
Frictionless connectivity
-
No-code REST integrations
Describe your API calls in a visual interface, with no development.
-
Every authentication mode
None, API Key (header/query), Bearer, Basic, OAuth2.
-
Preconfigured catalogue
Start from ready-made integrations and adapt them to your needs.
-
Global variables
Centralize your reusable parameters and propagate them to every integration.
Frequently asked questions about integrations
Do we have to migrate our data to connect a system?
No. K.IOP does not move your data: the source stays where it is and K.IOP reads it to build your tables. It only writes into your tools through a workflow you have created.
Which authentication modes are supported?
None, API Key in a header or a query parameter, Bearer, Basic and OAuth2, managed or custom-built. A connector can be global or carried by each user.
How is an integration triggered?
An integration does not run on its own: a workflow or the AI assistant calls it. The workflow starts by hand, on a schedule (from every 5 minutes to once a month), on an external webhook call, on a new item in a connected service (a message received, a row added), or on a K.IOP event: a row added or changed in a table, a file import finished, a dashboard alert firing.
See workflowsHow does data from an API get into a table?
Through a workflow: it calls the integration, on a schedule for instance, then the “Write to a table” step adds rows, updates the matching ones, or updates and otherwise adds. The table’s cleaning rules apply to every write.
Can I import an Excel or CSV file?
Yes, with no integration. An .xlsx, .xlsm or .csv file up to 64 MB becomes one table per ticked sheet. The header row is detected and each column’s type is guessed.
Can a workflow call any URL?
No. No step makes a free-form HTTP request: every outgoing call goes through an integration, with its credentials, its limits and its log. You always know which systems your data goes to.
Further down the chain
-
Refine
Data quality
Collected data is cleaned, deduplicated and reconciled before it reaches your dashboards.
Explore data quality -
Operate
Dashboards
Indicators are recomputed on refined data, never on an export.
Explore dashboards -
Security
Your connector credentials
OAuth2, ApiKey, Bearer, Basic: never in clear text, never shown again after entry.
Connect your systems
Book a demo to connect your first system live.
- No migration
- No migration
- Secure hosting