Start here · Lesson 1.6
12 AI App Integration Examples You Can Adapt
It is hard to start AI app integration from nothing. A list of examples gives you something to copy. Below are twelve ideas across different kinds of work, each with the apps involved, a sample question, why it is a good fit and the limit to set.
These are illustrative scenarios, not case studies, and I make no claims about results. Everything is built from what connectors are documented to do: access your apps and services, retrieve data and take actions, within your permissions. Lesson 1.6 shows how to connect the apps behind them: Connect AI to the apps you already use.
Good examples share a shape: a repeated job, one or two apps, view access, and an answer you can check in seconds.
How to read each AI app integration example
Each example has four parts. The apps you would connect. A sample question you could ask. Why it works, which is the reason it suits AI. And a limit to set. Adapt the wording to your business, and check that your assistant has a connector for each app before you plan around it.
Email and calendar examples
1. The morning briefing
Apps: email, calendar. Ask: "What needs me today? List each item and where it came from." Why it works: it is daily, spans two apps and is easy to verify. Limit: view access only.
2. The unanswered list
Apps: email. Ask: "Which people have I not replied to in more than a week? Show the subject lines." Why it works: finding gaps is tedious by hand and checking each hit takes a click. Limit: read only, no sending.
3. The meeting prep note
Apps: calendar, email. Ask: "I have a call with this client at three. Summarise our recent emails and what we agreed." Why it works: it pulls scattered context into one place. Limit: read only, and open the original emails for anything that matters.
4. The scheduling check
Apps: calendar. Ask: "Find two free hour long slots next week that are not on a Friday." Why it works: it is a lookup with an obvious check. Limit: do not let it create or change events without approval.
File and document examples
5. The latest version finder
Apps: file storage. Ask: "Find the most recent quote I sent to the garage." Why it works: searching a large folder is slow and the result is quick to confirm. Limit: connect only the folders the job needs, if your provider allows it.
6. The folder summary
Apps: file storage. Ask: "List the documents in the Q3 clients folder with a one line description of each." Why it works: it gives you a map of a messy folder. Limit: read only, never delete or move.
7. The template locator
Apps: file storage. Ask: "Find the contract template I used for the last design project." Why it works: you reuse good work instead of rebuilding it. Limit: review the template yourself before sending.
8. The draft starter
Apps: files, email. Ask: "Draft a reply to this client using our proposal as a reference. Do not send." Why it works: it saves the blank page. Limit: draft only, approval for any send.
Examples for specific kinds of work
9. The freelancer's invoice chase
Apps: email. Ask: "List the invoices I sent over 30 days ago with no reply." Why it works: it prompts you to chase money. Limit: read only. Write the reminder yourself or approve a draft.
10. The creator's collaboration inbox
Apps: email, a folder of briefs. Ask: "Which brand emails this month mention a deadline?" Why it works: deadlines hide in long threads. Limit: read only, and check each deadline in the original.
11. The shop's order check
Apps: the inbox that receives order notices. Ask: "Which orders are waiting to be shipped according to my emails?" Why it works: it summarises many short notices. Limit: read only, and treat the shop's own system as the source of truth.
12. The weekly review
Apps: email, calendar, files. Ask: "What did I commit to this week, and what is still open?" Why it works: it pulls commitments from several places. Limit: read only, and spot check against your own notes. This is the one to add last, since it touches three apps.
All twelve at a glance
| # | Example | Apps | Access level |
|---|---|---|---|
| 1 | Morning briefing | Email, calendar | View |
| 2 | Unanswered list | View | |
| 3 | Meeting prep | Calendar, email | View |
| 4 | Scheduling check | Calendar | View |
| 5 | Latest version finder | Files | View |
| 6 | Folder summary | Files | View |
| 7 | Template locator | Files | View |
| 8 | Draft starter | Files, email | View, drafts on approval |
| 9 | Invoice chase | View | |
| 10 | Collaboration inbox | Email, files | View |
| 11 | Order check | View | |
| 12 | Weekly review | Email, calendar, files | View |
Eleven of twelve are view only, on purpose. Start there.
Which one to start with
If you only try one, try the morning briefing. It uses the two most common apps and is easy to verify. If you work mostly with documents, begin with the latest version finder instead. Add the others a week at a time, following the CONNECT framework.
Limits that apply to all twelve
Several rules apply to every example. Ask for a source with each answer. Test on a question you know first. And remember that an assistant reading your inbox reads text from strangers. OWASP lists prompt injection, which is manipulating a model with crafted input, as the top risk for language model applications. So the examples above stay read only or draft only, and anything that sends, pays or deletes needs your approval.
Also check your providers' scope options. Google's Gmail documentation shows that viewing messages is a separate permission from sending and from permanently deleting, so a view only connection is a real option, not just a setting in the assistant. And Claude's help page says that connectors inherit your permissions in the source system, so the assistant sees what you see.
Making the examples your own
- Swap the nounsReplace "client" with customer, patient, sponsor or student, and keep the shape.
- Narrow the scopeAdd a date range or a folder name so the answer stays focused.
- Add the source lineEnd every question with "show where each point came from".
- Test itTry it first on a case where you know the answer.
- Note itAdd the example and its access level to your one page record. See Free AI app integration template: copy, fill, ship.
Questions people ask
Can I use these with any AI assistant?
Only where the assistant has a connector or similar link for the apps in question. Check its directory first.
Are these proven to save time?
No. They are plausible uses built from documented features. Time one yourself before assuming a saving.
Is it fine to use these with client data?
That depends on your agreements and the rules in your field. Check them before connecting client material, and leave sensitive folders out if unsure.
Pick one and begin
Twelve ideas is more than you need. Pick one, set it up with the narrowest access, and use it for a week. The guided steps for connecting your email, calendar and files are in Lesson 1.6: Connect AI to the apps you already use.