What can be connected
Only the data and operations your organization approves.
Resources, fields and operations are scoped during connector review. An AI employee never receives blanket account access simply because a connector page exists.
Ecosystem route · Assessment required
Infobip × ServAI
Infobip is available as a ServAI ecosystem integration route. ServAI selects an approved governed n8n, REST/GraphQL, webhook or enterprise-adapter path for the tenant; this page does not claim a pre-connected account.
CategoryProductivity & Collaboration
Connection routeGoverned n8n / API assessment
Data scopeLeast privilege
ActivationAdmission + health required
Connection setup
1 · Review the Infobip route
ServAI confirms the supported Infobip authentication method, API or n8n path, and the exact operations the role is allowed to request.
2 · Bind credentials
Secrets stay in the ServAI vault or the approved customer-owned credential store.
3 · Admit policy
Read, write, approval and data boundaries are attached to the connector manifest.
4 · Pass health
The connector is not operational until its tenant-specific health check succeeds.
Governance
Least privilege
Read, write and approval authority are separated by operation.
Traceable execution
Requests record connector identity, operation, policy decision and result evidence.
Fail closed
Unknown, unreviewed or unhealthy routes do not execute.
How AI employees use it
Role manifests request capabilities — not vendor-wide access.
A ServAI role pack can request an approved business capability. The connector registry resolves that request to this tenant's admitted connector only when the required permission, operation and health state are present.
What this page does not claim
No pre-connected account
This listing does not mean ServAI already has your credentials or an active customer connection.
No unlimited write authority
Write operations require explicit scope and may require human approval.
Next step
Turn the route into an operational connector.
Start an assessment so ServAI can confirm the integration method, data scope, credentials, workflow identity and health requirements.