External system connectionsConnect the tools your work already uses
Bring configured external services into the steps where your team needs them.
See connection status
Enable services as needed
Route exceptions to staff
From question to next step
Choose an external service
Set up authorization
Check connection status
Handle exceptions
What can connect
Configure a query or action supported by the external system. An import previews candidate operations and fields; it does not make every external API work without setup.
Operations and data scope
Begin with the interface the external system actually provides. Importing JSON or OpenAPI 3 shows candidate operations, paths, fields and types; it does not make a working tool by itself. Staff should check each field's meaning, required record identifiers and what data a response may contain. Public descriptions should explain the customer-facing service, while credentials and private responses stay in protected workflows. If the specification differs from a real response, correct the configuration after testing instead of asking the assistant to guess a field.
Set up the connection
Create a connection in the business dashboard, review imported fields and types, and configure the required endpoint and credentials. Test, enable and assign operations according to the business plan and staff permissions. Keep credentials in the protected account area, away from public pages and customer conversations.
Permissions and customer confirmation
Authorized staff create, test, enable and assign connections. The business's plan and the external system's authorization also determine available operations. Evaluate read-only lookups separately from writes that change external records. For a booking, order or other write, show the customer the target, time, quantity or other material details and obtain explicit confirmation before execution. A display name is not a substitute for an identifier required by the external API; resolve the correct identifier through a trusted lookup.
Limits and ownership
Available operations depend on the plan, permissions, connection setup and external system status. After import, review field mappings and test actual responses. A failed external action must not be described as completed.
Checks before enabling
Use suitable test data to check field types, required values, expired authorization, missing records and delayed responses. Decide which results customers may see and which only staff may see. Exercise success, failure and uncertain outcomes so the assistant does not report a failed action as complete or repeat a write. If the provider changes an interface or credentials expire, pause affected operations and verify them again. Public claims should match the capabilities actually configured and tested.
Common questions
Can I use an imported operation immediately?
No. Review the preview, configure the connection and credentials, check permissions, test, enable and assign it, then verify the result.
What if the external system needs an ID?
Get the correct identifier through that system's interface; do not put a display name in a field that requires an ID.
Does import make an operation customer-ready?
No. Review fields, authorization, tests and assignment.
Can an API key be put in knowledge?
No. Keep credentials in protected configuration.
What if the external system does not confirm success?
Describe the result as unconfirmed and ask staff to check.
Start with a real need
Tell us how your team serves customers today, and we can find a useful starting point together.
Request a trial