#1175 - Omnichannel Communication with Infobip

 

Introduction

Infobip Omnichannel is a cloud-based communication platform that unifies multiple marketing and support channels—including SMS, WhatsApp, email, and RCS—into a single, continuous conversation flow. By linking these touchpoints to a central customer data platform, it allows businesses to track customer history and context in real time. This ensures that users never have to repeat themselves when switching between automated chatbots, human agents, or different messaging apps.

So how do we leverage such value-add from OIC? Here's a simple demo of using the OIC Infobip adapter to send WhatsApp messages from OIC.

OIC Infobip Adapter

The Infobip adapter is available for download on the Integration Store - 

The adapter is now available in your connections list -

Invoking Infobip Omnichannel

As you can see, I need an api key to configure the connection. This I get from the Omnichannel portal - 

I need to specify scopes - for this demo I will be leveraging WhatsApp from OIC. I will also be looking at mcp, so this is reflected in my choice of scopes -

Under Channels, I choose all of the WhatsApp options.

You can check out the infobip docs here.

Back to my connection configuration - 

Looks good!

Now to a simple integration that sends a WhatsApp message.

Check out the actions supported - 

I see the numbers available to me - 

These numbers have been made available to me by Infobip; normally your number(s) would appear here.

The next page shows templates, these could be templates you have created and registered with Meta. Imagine a template for an initial marketing message to your customers. The template will have placeholders to which you can assign relevant values.

You can check out the template creation docs here.

This is the target structure you will see in the OIC mapper -

My template is called loyalty_promo and just includes the some text, akin to Dear {{Name}} we're thankful to have you as our customer. As a token of our appreciation we'd like to offer you {{NN}} % off on your next purchase...

Infobip expects the following payload format for this specific invoke - 

{

  "messages": [

    {

      "from": "YourFromNr",

      "to": "{{DESTINATION}}",

      "content": {

        "templateName": "loyalty_promo",

        "templateData": {

          "body": {

            "placeholders": [yourName, your%discount]

          }

        },

        "language": "en"

      }

    }

  ]

}

So I do the required mappings and test -

I've externalized most of the values in a lookup.

Let's test, by offering Renate a discount of 30%.

I check my phone - 

 



 







 

#1174 - Processing large files in OIC

Introduction

This post is just a couple of notes, primarily for myself, but maybe of interest to others.

The use case is simple - 

• list files in /inbox on OIC File Server
• for each file -
• invoke an async integration to write the file to an on-premise directory

This is implemented by a scheduled integration that uses the OIC File Server Native Action to list the files in /inbox. It then invokes an async integration for each file; it that does the following -

• check file size
• if >= 10MB
• use the FTP adapter to get the file reference from OIC File Server
• else
• use the OIC File server native action to get the file reference from OIC File Server
• file ref used as input to File Adapter - Write File - invoke

Test 1

The async integration is as follows -

Here I use the file server native action to get the file ref. I then map to target as follows - 

I run the test - 

Scheduled integration lists 2 files - 

Only 1 is written to my on-premise directory - 

I check out the activity stream for the largeFile processing - 

I amend the async flow as follows - 

I use the FTP adapter (download) operation to get the reference to the large file. Naturally, the FTP connection is to my OIC File Server.

I run the integration again - 

Note, in the mapper for LargeFileWrite I just map source fileRef to target FileRef, i.e. no encode to ref(decode to ref) logic. This logic is required for the other path though.

Net, net, we need to use the FTP adapter for files greater than 10MB.

#1173 - OIC 26.10 - MCP Gateway

Introduction

The MCP Gateway is a compelling new addition to the OIC Agentic toolkit. Released with 26.10, this gateway supports not just OIC based MCP servers, but also 3rd parties.

Please check out the excellent post from my colleague, Kishore, before continuing here. Kishore and his team have created a very compelling addition to our OIC Agentic AI Toolkit; well done, guys! 
Now that you have the intel, let's begin by exposing our 3 integrations below as Agent Tools. We also enable the Project as an MCP Server - 

MCP Gateway

Now to the MCP Gateway, let's add the MCP Server we just enabled - 

Step 1 is completed - we have included our OIC project MCP server definition in the context of MCP Gateway.

Let's look at the Security Policies we can apply.

Security Policies

With this initial release we support 2 policies - 

• PII Detection
• Tool filter

Let's check out PII Detection - 

There's a rich OOTB list, however, you can also add your own RegEx based pattern.

Note the 3 tabs - Detection, Enforcement and Action.

Detection is doing the actual work of detecting whether the payload contains an email address etc.  This work is done by OCI Gen AI service, so one needs to select an OCI compartment where this service is available.  

Back to the policy I chose; I can now specify how I want the policy applied - where and how.

Enforcement - this is the where. So where do I want to enforce the policy?

The options available are -

The Enforcement tab offers rich selection criteria; you choose what makes business sense to you.

Finally, the Redaction - here I define how I want to handle PII. 

Choices include - 

Again, we are offered a rich set of combinations.

I choose the following - 

At this stage, my Security Policy has been successfully configured; let's review my settings, before continuing -

Time to add the MCP Gateway - 

Note again, the optimal flexibility we are offered here. This is one of the hallmarks of our offering.

Activate - 

Click Run to get endpoint details -

 

Over to MCPJam - check out my intro post on MCPJam, if you're hearing about it for the first time.

Let's try out GET_CUSTOMER - 

Here's the customer row in the DB -

Back in OIC Project Observability -

the integration returns the email value and the gateway masks it.

Business Policies

I add the following policy - 

I add the customer, Cathal Brugha, to the DB -

Summa Summarum

This is a compelling addition to the OIC project toolkit. This gateway is not simply for OIC MCP servers but can be used with 3rd parties as well. It provides -

• identity and access control
• ability to cherry pick which tools are exposed
• ability to apply inbound/outbound policies
• OOTB auditing and observability

Please do take into account this is the initial release, so expect more functionality appearing in upcoming releases.

Cerevisia Aestiva

Today's beer is from Starnberg, the idyllic lakeside town, beside Munich -

On draught, this is a great summer beer; an optimal refreshing mix of malt and hops. At 4.8%, it's not the strongest, but the taste is still compelling. This is a very young brewery, founded in 2015; long may they continue! 

Sláinte is táinte.