Read a current record
Check a request’s status through a read-only tool. The provider describes its inputs and returns evidence from your system of record.
Example: request.status(reference)Read the guideIntegrations
Your systems. A more useful conversation.
Connect the information and actions your agent needs. Keep your existing software as the home of your business records.
Follow a request.
A connection gives an agent a specific capability. The request and its permissions decide what happens next.
The customer’s request
“Where is my request?”
- Your agentUnderstand the request
- Read request statusRead access
- Request systemThe next step
An answer from the current record
The agent asks the connected system for the request’s status. That system remains the source of the information. Answering the question does not require changing the record.
The customer’s request
“Can you create a service request?”
- Your agentUnderstand the request
- Allow request creationA permitted action
- Service systemThe next step
Confirmation from the recorded outcome
The agent gathers the required details and uses the operation you permit. A confirmation follows a recorded result. If the outcome is unknown, it needs checking before the action is retried.
The customer’s request
“I need an exception to the policy.”
- Your agentUnderstand the request
- Team approval requiredA human decision
- Your teamThe next step
Context ready for review
A request outside the agent’s authority needs your team’s decision. Review the conversation and recorded outcomes; the handoff workflow must be agreed and enabled during setup.
Connect what the job calls for.
Start with the workflow. Then choose its sources, actions and conversation channel.
Publish reviewed knowledge
Organize TXT and Markdown documents in collections. Follow ingestion jobs, review the exact version and keep approved policies available to your agent.
Collections → versions → reviewRead the guidePerform a permitted action
Expose a separate tool for creating or updating a record. Each mutation has an operation identity and a receipt to check if the connection times out.
Operation-Id + recorded outcomeRead the guideConnect WhatsApp messages
The Cloud API adapter verifies incoming callbacks, stores messages and tracks outgoing acceptance and delivery receipts. Your business number is configured during setup.
Verified message → agent → deliveryRead the guideThese capabilities are implemented in the backend. Connecting a particular business system still requires its adapter, credentials and verification during setup.
Bring one workflow.We’ll map the connections.
You don’t need to arrive with an API specification. A clear description of how your team works is a useful starting point.
Tell us what you want to delegate- The job
- What request does your team handle repeatedly?
- The information
- Which system holds the live record? Who approves the policies?
- The permissions
- What may the agent read or change, and what needs review?
- The first pilot
- Which cases will we test, and who reviews the outcomes before expanding?
Building the connection yourself?
Follow the request lifecycle, then use the guides for scoped credentials, agents, conversations and safe retries.
Let’s connect a useful first task.
Tell us what you use today and what you want your agent to do.