I’m working for a client building an interface that should replicate Outlook email interface.
The workflow would basically work by setting a webhook that is triggered whenever a new email is received in inbox, and creates a data object in Bubble with the information of the email (subject, body, messageID, thread, etc)
I’m using Graph API that is a built-in function with Microsoft Azure, but I can’t figure out how to parse email information in the webhook.
I know that with Make.com, this is a pretty easy thing to do (watch email module), but I’d like to keep everything in Bubble.
Would love to hear some feedback from someone that done it in the past
I figured out Graph API and built a fully functional ticketing app for a +100 user company that parses email conversation as tickets and sends email from shared email accounts.
For anyone thinking about creating this type of app, I would recommend using an externalised backend service like Xano as it gives a lot more flexibility for medium to high complexity backend cablework (webhooks to catch incoming emails, managing attachments).
I’m positive this could be done using 100% Bubble native backend, but I think for error handling and a better understanding of where API workflows get stuck, Xano does a better job.
Feel free to send me a message or reply in this conversation if you have any questions regarding this topic
