This document discusses integrating RingCentral SMS APIs with MuleSoft to build a notification module. It describes adding an API to an existing MuleSoft application that fetches SMS content by message ID and attachment ID. The API calls the RingCentral server, which returns the message content. This allows critical alerts to be sent via SMS as well as email, reaching external clients and customers who may not have email access.

1. Anirban Sen Chowdhary
Can Mule Integrate with RingCentral part 2?

2. As we have seen in our previous post the way of integrating RingCentral
with MuleSoft and sending SMS messages by consuming RingCentral
APIs.
We can present this as an important use case, where there can be a
requirement in a organisation to develop a notification kind of module
which will be attached with main MuleSoft application and can be used
to alert end-users, customers, clients or even production support team
via SMS message along with emails (which are mostly restricted to
organisation) during a particular application/server down or even any
unexpected exception occurred in the transaction of the application.

3. Extending our previous post, we will add one more API in our
application that will fetch the SMS contend via message id and
attachment id and display them to the users.
When we send a SMS message, RingCentral API send the message to
given phone number and create an unique message id and attachment
id for that particular SMS message. Every SMS will have those unique
Id.

4. We start by adding an additional API in our existing RAML specification
that will fetch those SMS message content as below:

5. As we can see above, we are passing dynamic yet unique message id
and attachment id to retrieve a particular SMS message.
After generation required flows from this RAML, we will add our
business logic in the below sub flow:

6. We can see that we are calling RingCentral API and passing the required
message id and attachment id to get the SMS content and display to
users.
We can also notice that, we are reusing OAuth 2.0 server call which is
wrapped in Cache block to reduce maximum call to OAuth 2.0 server
already discussed in our last post.

8. As we deploy our MuleSoft application, we can see our new API is
ready to take input for operation:

9. We are passing unique message id and attachment id to retrieve a
particular SMS message.
As soon as we hit the GET button, the API call RingCentral server and
fetch the particular message content based on message id and
attachment id below:

11. With the deadly combination of RingCentral with MuleSoft, a powerful
application can be created which will communicate via Cloud and send
message to the end-users, clients or support team in critical conditions
to their phones or organization phone along with traditional email
messages.
In many organization, emails are only restricted to organizational
environment and the clients and customer of the application has
limited access outside the organization, which otherwise solved by this
approach of sending SMS messages to phones breaking the boundaries
and alerting the stakeholders.