Exposed process automation

0

Hi everyone,

Currently i'm working with two applications, where one of them starts a workflow in second one. Let's call them Room Reservation, and Food Order.

I can request different types of food orders - breakfast, dinner, snack using Food Order application.
I can reserve a hotel room using Room Reservation application.

What i want to achieve is add the possibility to request a breakfast when reserving a hotel room.

I could do it currently in many ways, but there are two which i'd consider:
1. Have a dedicated action inside Room Reservation app, which would call Food Order.
2. Have a Global Automation which would be triggered from Room Reservation to call Food Order.

From those two i'd preffer 2nd option, as it somehow shows that this action is integrating with another app.
It separates the concern a little bit. It's like an interface.

I think we are missing something like 'Exposed process automations' - automation declared on process level, but exposed to be used in other applications.

This would allow us to create somewhat like interfaces, so applications won't be so tightly tangled up together.

It's achievable with Global Automations, but this way it doesn't directly tell us which process is the parent/owner.

I'm curious how you would handle this case, and if that separation of concerns is something you'd like to have ;)