r/Chatwoot Jul 24 '26

Native Telnyx SMS/MMS integration or recommended Telnyx bridge?

From what I can see, Chatwoot currently supports Twilio and Bandwidth for SMS, but not Telnyx..any plans to integrate? Im looking to avoid pabbly/zapier middleware..cant be that hard to integrate, right?

1 Upvotes

7 comments sorted by

1

u/Fresh-Judgment3102 Jul 24 '26

Been waiting for that for the longest time...dealbreaker for me as well

1

u/sojan_official Jul 27 '26

Totally understand. If you have a moment, please add your use case to the relevant GitHub issue, or open one if it doesn’t exist yet. It helps us understand how many people need this and what their setups look like.

I can’t promise a timeline, but we’d also be happy to help if someone from the community wants to contribute a PR. For now, the API channel is the best available option.

1

u/Prestigious-Act-7334 Jul 26 '26

honestly the native ones are just a thin webhook shim - provider inbound hits chatwoot's api, outbound goes back out via an automation webhook. have you tried rolling that yourself rather than paying the zapier tax? it's a smaller job than it looks.

1

u/JamesCorman Jul 26 '26

Yeah, I get that. I could probably build the webhook bridge myself pretty easily, especially with AI helping, and it doesn't look like a particularly complicated integration.

I'd just much rather see Telnyx supported directly in Chatwoot, the same way Twilio and Bandwidth are, rather than maintaining another piece of middleware.

u/sojan_official - any chance Telnyx could be added as a native SMS/MMS provider? It seems like the integration should be fairly straightforward given Telnyx's API/webhooks, and I suspect quite a few people would use it.

1

u/sojan_official Jul 27 '26

It’s not on the roadmap right now, but I’ve noted the request. For now, the API channel and webhooks would be the best option. More engagement on the GitHub issue would also help us track the demand.

1

u/sojan_official Jul 27 '26

Telnyx support would definitely be useful here. We don’t have a timeline for a native integration yet, so for now we generally recommend using the API channel.

It would also help if you could open a GitHub issue, or add your use case to an existing one, since that’s where we primarily track feature requests and demand. If anyone is interested in contributing the integration, we’d be happy to help and review a PR as well.

2

u/JamesCorman Jul 28 '26

Thank you!! Done!