Integration with actions, tag changeability feature

[ibrahimAlbyrk]

Is your feature request related to a problem? Please describe.

Currently, when creating a new conversation via the "Integration with Actions" system in Omi, the tag is automatically assigned based on Omi’s internal categorization. However, this is often too broad or not fully representative of the content.

For example:

• If an email arrives from GitHub, Omi assigns the tag Technology, but a GitHub tag would allow for more specific filtering.
• If I convert bills into conversations, they might be tagged as Finance, whereas a Payments tag would be more precise.

While Omi can already list conversations based on their content (e.g., "Show my technology-related content" lists all technology-related items), more specific tags would allow users to refine their queries further.

For instance:

• Instead of searching "Show my technology-related content", I could say "Show my GitHub-related content".
• Instead of "Show my finance content", I could say "Show my pending payments".

This would provide better organization and clarity when managing conversations.

---

Describe the solution you'd like

I would like the ability to manually define or modify tags when creating a conversation via API. Specifically:

• Allow API users to set a custom tag when a conversation is created.
• If no tag is provided, Omi can still auto-assign one.
• Provide an option to edit the tag later if needed.
• And the ability to add multiple tags (For example, if it is a payment on github, I would like to add both github and payment tags.)

This would enable users to filter conversations more effectively and retrieve specific information faster.

---

Additional context

Example use case:

Current Behavior:

1. An email from [email protected] arrives.
2. A conversation is created via API.
3. Omi assigns the Technology tag.
4. I can ask "Show my technology-related content", but this includes all technology-related items, not just GitHub.

Desired Behavior:

1. The same email arrives.
2. I pass { "tag": "GitHub" } while creating the conversation.
3. Omi stores it with the correct tag.
4. Now, I can say "Show my GitHub-related content", and only relevant conversations will be listed.

This feature would significantly improve organization, filtering, and user experience, making it easier to retrieve relevant conversations in a structured way.

[ibrahimAlbyrk]

Examples;

my outputs

Omi standart summary