Pipeworks really talks well with Twilio. So well, in fact, that you don't really have to think about it. You just have to think about how your cmdlet works.

Every command that you expose as a web service implicitly can be talked to via text. The way it works is pretty simple, but can be pretty dangerous if you let the wrong command work.

Text messages from Twilio come with a number of request parameters. Any of these parameters that are found on your function get passed in the value Twilio sends you. Any other parameters get passed in positionally.

When the output comes back from the command as text, it's sent directly to the user. If it's anything else, each property of the object is show on a different line of the text message.