WhatsApp native integration

@sapter @vincent Ghost Team @Mav. today or tomorrow I'll try to define stages of WhatsApp native integration with Twenty roadmap in mind, so you could later discuss the implementation details
20 Replies
ɃØĦɆᵾS
ɃØĦɆᵾSOP7d ago
Just to be clear, it's gonna be an implementation completely done by community but overseen by core team as core team has different features to implement We can also use the VoIP integration done by @sourcedandsoldtothehighestbidder once PR is prepared and approved by core team More info here: https://discord.com/channels/1130383047699738754/1130383048173682821/1441634270698541056
sourcedandsoldtothehighestbidder
it has to be built ontop of waha with rotating proxies
ɃØĦɆᵾS
ɃØĦɆᵾSOP7d ago
Waha?
sourcedandsoldtothehighestbidder
waha is an opensourced framework to basically to programatic interactions with whatsapp via an unofficial api
sourcedandsoldtothehighestbidder
you can use baileys but this here is faster to get to prod https://waha.devlike.pro/docs/overview/introduction/
WAHA
📖 Introduction
WAHA - WhatsApp API that you can install on your own server and run in less than 5 minutes!
ɃØĦɆᵾS
ɃØĦɆᵾSOP7d ago
I think that's gonna be a later stage, messages are more important imo But like I've said, I'll try to plan stages either today or tomorrow as I'm currently less available than normally
sourcedandsoldtothehighestbidder
GitHub
GitHub - devlikeapro/waha: WAHA - WhatsApp HTTP API (REST API) that...
WAHA - WhatsApp HTTP API (REST API) that you can configure in a click! 3 engines: WEBJS (browser based), NOWEB (websocket nodejs), GOWS (websocket go) - devlikeapro/waha
sourcedandsoldtothehighestbidder
I use it on my own selfhosted instance and it works well for sending and recieving messages just obviously cannot over do it.
ɃØĦɆᵾS
ɃØĦɆᵾSOP7d ago
Probably the best timing would be around call recorder feature
sourcedandsoldtothehighestbidder
Yeah I made a way inside of my crm to basically multipart form upload audio
ɃØĦɆᵾS
ɃØĦɆᵾSOP7d ago
DRAFT Stages of integration: 1 - reading all conversations, adding people to Twenty from WhatsApp if they don't exist in Twenty and adding a mechanism for importing newest messages based on webhook 2 - sending WhatsApp messages directly from Twenty 3 - reading files from WhatsApp messages and attaching them to People records 4 - calling WhatsApp people directly in Twenty 5 - recoding the calls, transcribing them and attaching to People records
sourcedandsoldtothehighestbidder
Would this here be adjusted from the email component for sync Everything here is more than feasible - I saw in the documentation that many to many relaitons would be good but that's not intergrated yet until Q1 2026 But what I think would be needed is an entry point because if we're able to just have it so that we're able to basically to make it so that there is a sync engine between backend to postgres would make life smooth sailing If we adjusted the Email component to then adopt it for messaging we could have the custom wa field I spoke with another person who was working on a bailey intergration which is the library itself but I tried intergrating bailey before and it was way too dificult rather than just having a http swagger endpoitn which can be adapted very quickly
ɃØĦɆᵾS
ɃØĦɆᵾSOP7d ago
Write down anything that is necessary in your opinion and, I'll adjust it, I'll also check more documentation to see what features may be necessary for businesses, it's a draft currently after all I'd rather implement this in Integrations tab or change the Email tab into Messages tab and add subtabs
Unknown User
Unknown User7d ago
Message Not Public
Sign In & Join Server To View
ɃØĦɆᵾS
ɃØĦɆᵾSOP6d ago
Then first stage would be abstracting everything message related but it's already planned for second half of next year as per message here https://discord.com/channels/1130383047699738754/1130383048173682821/1440735022993768599 @Thomas @Prastoin do you think it'd be possible to handle this by community?
sourcedandsoldtothehighestbidder
Yeah I agree but if we look at it like a service which we then can map and define a swagger rpc so we have a unified interface for updating on the macro level so all unififed functions messages groups reactions media for example reuse components inside of the object structures that are native for example multipart attachmnets that get transformed to the type thats accessed via the api for respective platforms
Unknown User
Unknown User6d ago
Message Not Public
Sign In & Join Server To View
sourcedandsoldtothehighestbidder
@bob did you make these here
No description
ɃØĦɆᵾS
ɃØĦɆᵾSOP4d ago
These are generated dynamically by the engine
sourcedandsoldtothehighestbidder
I think this is the best place where we can have the entry point for whatsapp and the other stuff

Did you find this page helpful?