We want a way for anyone who builds to claim ownership of their buildings, and a way for them to reference their building.

That is why we wanted to take advantage of Link Mobility’s SMS API. But we also wanted to do it as a low-code solution.

That is why we wanted to create a custom connector towards the API:

Configuring the connector

We chose the basic authentication method of the API. But we didn’t want to enter the platform partner ID every time we added the action. So we used paconn to edit the apiProperties.json file to add that as an extra parameter when creating the connection.
Like this:

apiProperties.json

Here we’re creating a custom Policy Template that adds the platformPartnerId parameter to the JSON in the body of the call.

Here is the flow that sends the SMS. It triggers when a row in our Minecraft Building table is added with a Owning Minecraft User or the Owning Minecraft User is updated with a value.

It then gets the Owning Minecraft User(It is just a relationship to the contact table) and checks if we have their mobile number and sends the SMS if we have it. The SMS contains the name of the Minecraft user as well as the name column of the Minecraft Building table which should be a unique name.

The action (in action):

PS! We don’t want anyone to answer the SMS so we’re using a shortcode as the sending number.