# Building Apps

## What apps you can build

Here are some categories of App you can build, nevertheless, the possibilities are endless, the only limit is your imagination ? You can Also create an app that mixes multiple kinds

1. **Actions on External Apps**\
   Example: Hubspot, Pipedrive, Jira\
   In this kind of Apps, you can create, fetch & update records in external Apps right from Chat Inbox. To trigger this workflow, use menus, actions on messages triggers or actions on Adaptive Cards. Use AdaptiveCards views for a better user experience
2. **Notification App**\
   Get Notifications from an External App or a workflow
3. **Process Messages** \
   Exp: translate, moderate ??, remind, schedule a message (one time or multiple times)\
   These Apps use external APIs or custom functions to process messages.\
   tips: *Use Sidebar, messages only visible to you , threads*
4. **Send a Rich Interactive Card**\
   (Custom Button or Component)\
   Example: Pay with Stripe, Calendly Button, Zoom Link, Upload Document with Cloudinary, Send a Rich Post,..\
   This App empower the user with the ability to post a Rich Message to the room with his won name
5. **Chatbot (Internal or External)**\
   (with tekos, or external messaging: telegram, whatsapp,..)\
   \&#xNAN;*tips: use human handover (bridget feature+invite an operator) for a better user experience*
6. **Bridge Bot**\
   roots messages from external messaging to your inbox\
   \&#xNAN;*tips: combine chatbot feature with bridge to send a first welcome message, useful when you are off*
7. **Store & Manage Custom Objects (CRUD)**\
   Exemples, 1:1 ticketing, 1:n orders. usually combined with labelling & tagging rooms\
   **Add Workflows**
8. **Standalone workflows**\
   (no interaction with Tekos Chat) do we need to to it?\
   \=> collaborate with your team on the flow?


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://tekos.gitbook.io/doc/building-apps-1/building-apps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.