Meta component Separation Solution

[M-Shorouk]

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

Currently on Meta Developers one could enable "Messenger Business" (FB), Instagram Messenger, & "Whatsapp Business Cloud" from same Business App on Meta developer platform. However, as an Airy user, i need to configure "Messenger Business" (FB), "Instagram Messenger", & "Whatsapp Business Cloud" components on its own.

Describe the solution you'd like

From the discussion carried out HERE, we opt first Solution;

1. FIRST SOLUTION

[Component : Connector is 1:1]

Separating [channel_types] as own components , { Messenger Business, Instagram Messenger, Whatsapp Business Cloud }since each [channel_type] needs its own configuration.

In this solution, for a successful install, Airy user will need to Configure different components for Meta "connectors".

Airy user would be able to install " Business Messenger" component and "Instagram Messenger" component and configure them on their own; Connecting [channel-types] to your instance will require separate components configuration :

COMPONENT CONFIGURATION :

COMPONENT 1: "Business Messenger":

• App ID : APP_ID
• App Secret : APP_SECRET
• Webhook Secret APP_SECRET/WEBHOOK

COMPONENT 2: "Instagram Messenger" :

• App ID : APP_ID
• App Secret : APP_SECRET
• Webhook Secret APP_SECRET/WEBHOOK

COMPONENT 3: " Whatsapp Business Cloud"

• App ID : APP_ID
• App Secret : APP_SECRET
• Webhook Secret APP_SECRET/WEBHOOK

ADDING CHANNEL PER COMPONENT CONFIGURATION"

CONNECTOR 1 : "Business Messenger"

• page_id : is the Facebook page ID.
• page_token : is the page Access Token.
• name : is the custom name for the connected page.
• image_url: (optional) is the custom image URL.

CONNECTOR 2 : "Instagram Messenger"

• page_id : is ID of the Facebook page connected to the Instagram account.
• page_token : is the Access Token of the Facebook page
• account_id : is the ID of the Instagram account
• name : is the custom name for the connected page
• image_url : (optional) is the custom image URL.

CONNECTOR 3 : "Whatsapp Business Cloud" :

• phone_number_id : the whatsapp phone number connected to your business account.
• user_token : your user access token.
• name : is the custom name for the connected page.
• image_url : (optional) is a custom image url for displaying this channel on the UI.

Technical drawbacks:

• We have to package each [channel-type] as a component separately which will create redundancy of Meta connector code.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

[AitorAlgorta]

I think this is good to go.