Hello,
We have business need to allow our apps to exchange data with each other.
The current state of Forge App Events has currently the following limitations :
Is there any ETA for these limitations to be removed ?
The only other way we could figure out to allow such inter app communication would be using Web Triggers. This comes with quite some pain in term of exchanging URLs to clients.
FYI, it seems there was no trace of the removal of those limitations at Atlassian. Hence they created the following ticket : https://jira.atlassian.com/browse/ECO-1248 Please vote 
What is the purpose of App Events if it can’t cross apps with payload? How is a globally anonymous event name even useful? Is anybody even testing the preview?
At a minimum we need to be able to convey context.
e.g. Event #1: Training Completed
User ID: ?
Page ID: ?
e.g. Event #2: Jira Work Item Signed
Project ID: ?
Work Item Key: ?
User ID: ?
In the absence of payload, what we envisioned was to use it as notify to tell another app it should query for data using a webtrigger.
This is a much more complex architecture also considering there’s no easy way to share the web trigger urls between apps and also that web triggers will need an additional layer of security.
What a pity…
@GuillaumeBero, thanks for raising this. I appreciate that the current implementation has limitations which prevents a lot of use cases. I’d love to connect and chat further about your use case and what you’re wanting to build with x-app communication.
You can use this link to book in some time to chat.
