Progress
Cancelled
Completed
This was an impromptu task. We realised as we researched the WhatsApp API that OAuth was not used but rather an API bearer token was used. As such we started researching the Bearer token as an authentication method.
We used the following resources to familiarise ourselves with the development process of the connector. This process was particularly difficult as all the concepts learned were initially very unfamiliar, so understanding the relevance between each part of the connector was difficult.
We signed up for this Developer account and created the tenants such that we can all access Microsoft Development tools and Apps, such as Power Apps and Power Automate.
To be able to create the Meta app to handle the sending of messages, we need to be signed up as Developer with Meta. After doing that, we created our Meta App and configured it. Once configured, we followed steps to replace the temporary bearer token with a permanent one.
Ongoing
We had much more significant blockers when conducting this task. The setup of the developer account had too many security parameters such as asking for a company license and passport or identification documents. Furthermore, all the documentation was directly translated from Chinese to English without changing the semantics. Consequently, we were only be able to use and create a disposable sandbox developer account for WeChat for testing purposes.
WeChat Sandbox Developer Account
We began by testing the API call on Glitch as per the Meta documentation but migrated to Postman for further testing. This is because the connector allows us to import Postman collections but not Glitch code.
Glitch would allow us to configure a webhook which allowed two-way communication, but, as advised by our project partners and through our research, we would not be able to move this over to Power Platform.