Integration
A purchase request ends up in the ERP, an onboarding creates accounts in the directory, a complaint takes data from the CRM. Most processes need connections like these. In nexxcite, you set them up as a step in a flow, without a separate integration project.
Every direction
Supported standards
Two directions
A documented REST API with OAuth 2.0 sign-in. It uses the same processing as the interface: rules, calculations, checks and follow-up actions apply in the same way.
As a step in a flow, without a separate integration tool and without programming.
Same processing
A flow triggered via the API behaves like one started by a click
There is no second processing path for machine calls, no different checks and no special logic. In practice, this means: when you test a process in the interface, the API route is tested along with it.
Ready-made connections
Ready-made building blocks for directory operations: HR records the new joiner, and the flow creates the account, sets the initial password and maintains the groups. When someone leaves, it runs the other way.
Your identity management stays in charge: OpenID Connect, LDAP and Active Directory, user sync from the directory, OAuth 2.0 for connected systems.
Sending via SMTP and Exchange Online. Mailbox monitoring via IMAP and Exchange Online, with rules by sender, subject, content and attachment, including matching to existing cases.
Attachments do not have to live in the database: file system, Azure Blob Storage or S3-compatible storage, chosen per use case.
Often laborious in integration projects, included here: read, iterate and generate JSON, plus XML, Excel and CSV, and large files line by line.
Model Context Protocol (MCP) both ways: nexxcite provides tools, and external MCP servers are also made available to the assistant, including within flows.
An example
Name, department, start date and workplace are entered once, in the HR workspace's form.
The flow creates the user in Active Directory and assigns the department's groups.
Via an HTTP call to the leading system's API, with the values from the joiner record.
By email through Exchange Online, with a checklist for day one.
Before the start date, a schedule checks whether everything is done and escalates whatever is missing.
Configuration, not a project
A middleware tool, a service provider, a script on a server that nobody remembers after a while.
Configured where the process is defined: visible, protected by permissions and monitored.
FAQ
Anything that offers an HTTP API, through configured calls with authentication, with responses as JSON or XML. Plus file exchange via Excel, CSV, JSON and XML, and script and program calls on the server.
Yes. Scheduled flows fetch files from storage or call APIs and process the results, line by line if needed. Background jobs are monitored.
Centrally managed with their own permissions. Flows reference them instead of containing them.
Every installation ships an OpenAPI description and interactive documentation for its own version, including the record types set up in your system.
It is skipped and logged. The assistant carries on with the remaining tools.
Live demo
Tell us which systems matter most to connect. We will tell you whether each can be configured or means additional effort.