The tools your AI agent uses to finish the work
An AI agent tool is a connection that lets the agent act in one of your systems: read a document, check the calendar, send an email, open a ticket or call your own API. This page lists every tool the Tridan AI agent can use, the problem each one removes and whether it is ready now or connected in your setup.
22 tools in 7 areas of your business
What can the AI agent do in your systems?
Each card starts with the problem your team has today, then shows a real question and what the agent does with it. Tools are grouped by the part of the business they serve, not by technology.
Prefer to look by system? See integrations by category
How do you read a tool card?
Ready now: switched on in the agent's settings after you sign in to the service or add an API token, with no development work.
Connected in your setup: our engineers connect your system through its API as part of the setup project.
Asks for your approval: in website chat and dashboard chat, this action can be set to wait for a person's yes. Phone calls run without that pause.
Your documents and knowledge
The agent answers from what your company has already written, not from the internet.
Documents and price lists
Answers are buried in PDFs and spreadsheets that only one person knows how to search.
- Example
- βHow much is the annual service for 12 air conditioners?β
- What the agent does
- The agent searches the price list you uploaded and answers with the price and what it includes.
- Data from:
- PDF, Word, Excel, PowerPoint, image and text files you upload
Your website and YouTube videos
Your website already explains your services, but customers still call to ask.
- Example
- βDo you work on Saturdays?β
- What the agent does
- The agent answers from the website pages and video links you add to its knowledge.
- Data from:
- Pages of your website and YouTube links
Confluence and Notion pages
Procedures live in a wiki that nobody searches under time pressure.
- Example
- βWhat is our procedure for a refund after 14 days?β
- What the agent does
- The agent imports the pages into its knowledge and answers your team from them.
- Data from:
- Confluence and Notion pages you import
Reading a whole document
Some questions need the full contract or manual, not one paragraph of it.
- Example
- βSummarize the termination terms in our framework agreement.β
- What the agent does
- In chat, the agent opens the whole file and reads it end to end before it answers.
- Data from:
- Files in the agent's knowledge, or a PDF attached in the dashboard chat
Your email and calendar
The agent works in the inbox and calendar you already use, and you decide which actions wait for your yes.
Gmail
The inbox fills up with messages that each need a search and the same kind of reply.
- Example
- βFind Marko's last email about the offer and draft a reply.β
- What the agent does
- The agent searches Gmail, reads the thread and prepares a draft. It sends only when you allow it.
- Data from:
- Your Gmail account, connected with Google sign-in
Google Calendar
Agreeing on a meeting time takes three emails and a day of waiting.
- Example
- βBook a 30-minute call with Jelena on Thursday afternoon.β
- What the agent does
- The agent checks free and busy time, books the meeting and can move or cancel it later.
- Data from:
- Your Google Calendar, connected with Google sign-in
Outlook mail (Microsoft 365)
Your company runs on Microsoft 365, and email answers wait for someone at a desk.
- Example
- βDid the supplier reply about the delivery date?β
- What the agent does
- The agent reads your Outlook mail and sends replies from your Microsoft 365 account.
- Data from:
- Your Microsoft 365 mailbox, connected with Microsoft sign-in
Email from your own mail server
Your email is not on Gmail or Microsoft 365, but confirmations still have to go out.
- Example
- βSend the customer a confirmation with the offer attached.β
- What the agent does
- The agent sends the email through your mail server, with CC, BCC and attachments.
- Data from:
- Your SMTP mail server settings
Your customers and sales
The agent collects what your sales team needs and passes the conversation on when a person should take over.
Contact capture in the chat
Website visitors ask a question and leave without a name or a number.
- Example
- βCan someone call me about an offer?β
- What the agent does
- The agent opens a short contact form in the chat and saves name, email and phone together with the conversation.
- Data from:
- The website chat conversation
Questions and forms in the conversation
The agent needs a date, a number or a choice before it can continue.
- Example
- βI want to book a service.β
- What the agent does
- The agent asks for exactly what is missing, as a field, a choice or a confirmation, and continues with the answer.
- Data from:
- Answers typed in the website chat or the dashboard chat
Handover to your team
Some conversations need a person, and the customer should not have to start again.
- Example
- βI would like to talk to someone.β
- What the agent does
- The agent passes the conversation to your team with the whole history, so nobody asks the same question twice.
- Data from:
- The website chat conversation
LinkedIn posts
Company news waits for someone to find the time to write and publish the post.
- Example
- βWrite a short post about our new service and publish it once I check it.β
- What the agent does
- The agent writes the post and publishes it on your LinkedIn profile.
- Data from:
- Your LinkedIn account, connected with LinkedIn sign-in
Available on selected plans, contact us to enable.
Support and tasks
Requests that arrive in a conversation become tickets and tasks with the details already filled in.
Jira
Requests from chat and email are retyped into Jira, often without the details.
- Example
- βOpen a task for the broken invoice export and add it to the current sprint.β
- What the agent does
- The agent creates and updates issues, adds comments and moves tasks through your workflow and sprints.
- Data from:
- Your Jira Cloud, connected with an API token
Zendesk
Customer problems arrive in chat, but your support queue lives in Zendesk.
- Example
- βOur card reader stopped working this morning.β
- What the agent does
- The agent opens a Zendesk ticket with a summary of the conversation, and can check or update it later.
- Data from:
- Your Zendesk account, connected with an API token
Available on selected plans, contact us to enable.
Confluence pages
A procedure changes, but the wiki page is updated weeks later.
- Example
- βAdd the new return deadline to the Returns page.β
- What the agent does
- The agent searches, reads and edits Confluence pages and their comments.
- Data from:
- Your Confluence, connected with an API token
Your finances
Invoice and payment questions are answered from your own systems, connected through their API in your setup.
SEF e-invoices (Serbia)
Colleagues ask whether a sales invoice you issued was delivered or accepted on SEF, and someone logs in to check.
- Example
- βWas our sales invoice 245 accepted on SEF?β
- What the agent does
- The agent checks the status of your sales invoices in SEF through the official public API and answers with the current status.
- Data from:
- SEF, the Serbian e-invoicing system, through the official public API (API key from SEF, API management)
Your accounting software or ERP
Questions about open invoices and balances wait for the accountant to have a free moment.
- Example
- βWhich invoices for client IliΔ are still unpaid?β
- What the agent does
- The agent calls your accounting system's API and answers from the data it returns.
- Data from:
- Your accounting software or ERP, if it has an API
Your phone
On your phone line, the Call Center Voice Agent uses the same tools, without the approval pause.
The same tools during a call
Callers want a booking or a ticket, not a promise of a callback.
- Example
- βCan I come in on Friday morning?β
- What the agent does
- During the call, the voice agent checks the calendar, books the slot or opens the ticket with the tools you enable for calls.
- Data from:
- The tools you enable for the agent
Transfer to an operator
Some callers need a person right away.
- Example
- βPut me through to someone, please.β
- What the agent does
- On inbound calls, the voice agent transfers the caller to the operator number you define or to another menu.
- Data from:
- Your phone line settings
Phone number from the keypad
A phone number spoken aloud is easy to mishear.
- Example
- βPlease type your phone number on the keypad.β
- What the agent does
- The voice agent reads the digits the caller types on the phone keypad.
- Data from:
- The caller's phone keypad
Your systems
Anything else your team looks up can reach the agent through your API, plus current information from the web.
Your own API
The answer lives in your internal system, and only your staff can look it up.
- Example
- βHow many vacation days do I have left?β
- What the agent does
- The agent calls your system's endpoint with the parameters you define and answers from the data it returns.
- Data from:
- Your system's REST API, with the access key in the request headers
Web search and page reading
Some questions need current public information, such as a supplier's delivery terms.
- Example
- βCheck the supplier's website for their current delivery terms.β
- What the agent does
- The agent searches the web, reads the pages it finds and answers from what it read.
- Data from:
- Public web pages
Where does the agent take data from, and where is it processed?
The agent takes data only from the sources on its cards: files in its knowledge, the accounts you sign in with and the APIs you connect. It runs in the Tridan AI cloud, or self-hosted in your VPC or on-premises with local models through Ollama, and your data is never used to train AI models.
- You or your customerAsks a question
- AI agentUses only the tools you enable
- Your sourcesKnowledge files, accounts you sign in with, your APIs
- Where it runsTridan AI cloud or your servers
- Answer or actionBack in the same conversation
Need a tool that is not on the list?
If your system has an API, we can usually connect it in your setup with the custom API tool. Tell us which system and which task, and an engineer will tell you honestly what is possible.
Common questions about AI agent tools
Which AI agent tools are ready now, and which are connected in your setup?
Tools marked Ready now, such as your uploaded documents, Gmail, Google Calendar, Outlook mail, Jira, Zendesk and Confluence, are switched on in the agent's settings after you sign in to the service or add an API token. Tools marked Connected in your setup, such as SEF e-invoices, your accounting software or any other internal system, are connected through their API by our engineers as part of the setup project.
Which agent actions can require approval?
Actions in Gmail, Google Calendar, Outlook, your own mail server, LinkedIn, Jira, Zendesk and Confluence can each be set to require approval. In website chat and dashboard chat, the conversation then pauses until a person confirms. Calls to your own API, web search and phone calls run without that pause, so for them we connect read-only access wherever the task allows and enable only actions you are comfortable running directly.
Can the AI agent query our database directly?
No, the Tridan AI agent does not query your database on its own. When the data lives in a database, the usual route is a read-only API in front of it, provided by your team or ours, which the agent calls with the custom API tool. That keeps control on your side: the API decides which records and fields the agent can see, and nothing else in the database is reachable.
Does the AI agent see all our emails and documents?
The AI agent sees only what you connect to it. It answers from the files and pages you add to its knowledge, and it works in the Gmail, Outlook or Google Calendar account you sign in with for that agent. Each tool is switched on per agent, so a website agent for customers can have the price list and the calendar, while an internal agent for your team also gets Jira and Confluence.
Do we need a developer to use the agent's tools?
Not for the ready tools. You sign in to Google, Microsoft or LinkedIn, or paste an API token for Jira, Confluence or Zendesk, and switch the tool on for the agent. For your own systems, someone has to describe the API: the address, the parameters and the access key. Our engineers do that with you in the setup, and the custom API form in the dashboard stores it for the agent.
Last updated Β· Reviewed by Nemanja Milivojevic, Founder