Forge inter-app communication

Forge
, , ,
1

Hello,

We have a Forge App “A” using Forge SQL.

We would now like to interact (read, write, delete) with the data, which is part of app “A” from another app “B”.

Is there a way to do so?

Goal: “Runs on Atlassian” (which should be achievable imo as long as both apps do “run on Atlassian” and both apps are installed and approved by a customer)

Approaches:

  • built-in forge functionality for inter-app communication (call function in backend of “A” from frontend of “B”)
  • use of forge remote: make backend function of “A” available as remote somehow
  • use of forge remote for storage: access storage of “A” from “B” directly (currently not available for forge SQL?)
  • solution outside of forge: do not use forge SQL so that both apps have access (means losing any chance on “Runs on Atlassian”)
  • worst solution: mirror all the data from app “A” in app “B” via remote + triggers so that it can be accessed

Does anyone have any idea on how to achieve this? Every help would be much appreciated!

Best,

Paul

2

Hello @PaulLunkenheimer

You have a limited set of features you can use:

  • Store data in a commonly accessible storage, like Confluence or Jira. Store in standard entities or Entity/Content properties.
  • Web trigger: invokes a function as the result of an HTTP request.
    Use it to get app A data from app B
  • Use Forge App events App Events (Preview): to broadcast messages between backend instances.

For Atlassian, ideally I would love to get a common storage for all apps of the same editor (Developer Team). This mechanism exists in the mobile world for example, allowing all apps of the same editor to share stored data.

Hope that helps :slight_smile:

3

Hi @FabienLydoire,
Thank you so much for your response back in October. Never managed to get back to you.

A lot has happened and I think there are a few more workarounds, but I had a chat at the Atlas Camp in Amsterdam today and it looks like there is an internal Jira item for this feature (inter-app communication) but it is not on the public roadmap and there is no date set yet.

I’ll mark your answer as the best solution to my question at the time being, but for anything visiting in the future: I hope there will be another way. :grin:

Best,

Paul