Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow multiple triggers for Integration Apps #1753

Open
mdmohsin7 opened this issue Feb 4, 2025 · 0 comments
Open

Allow multiple triggers for Integration Apps #1753

mdmohsin7 opened this issue Feb 4, 2025 · 0 comments

Comments

@mdmohsin7
Copy link
Collaborator

mdmohsin7 commented Feb 4, 2025

Currently, Omi Apps can only utilize a single trigger, limiting their functionality. Some apps require multiple data points at the same time to operate effectively. Allowing app creators to select multiple trigger events instead of just one would enable them to consume different types of data through a single webhook, expanding the flexibility of their integrations.

Challenges

  • Single trigger limitation: Apps can only respond to one type of event, restricting their potential use cases.
  • Backend migration required: Transitioning to multi-trigger support necessitates updating existing app data and backend references to avoid breaking changes.

Proposed Enhancements

  1. Enable Multiple Trigger Selection:
    • Allow app creators to define and subscribe to multiple trigger events
  2. Backend Updates:
    • Migrate existing app data to support multiple triggers.
    • Update backend references to handle multiple trigger events seamlessly.

User Flow

  1. App creators navigate to the Submit App page.
  2. Select multiple trigger events from the available list instead of just one.
  3. Submit the app.
  4. The app receives and processes data from all selected triggers.

Benefits

Expands app capabilities: Apps can utilize multiple data points for richer functionality.

Enhances integration flexibility: Supports more complex workflows and automation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant