Baton SMS Integration

Implementation teams using Baton often have several projects moving through different statuses, and a missed status change can leave customers or colleagues waiting for an update. A Zap can send an SMS from Mobile Message when a project appears under a selected status, giving the responsible person a direct prompt without asking someone to check Baton repeatedly. The Templates trigger can also notify an operations list when a new template is created.

Baton’s Create Project action can be started by Mobile Message Inbound SMS Received when a text contains the information your process needs, although this should be used only where the project fields can be supplied reliably. For most teams, the clearest workflow is a Baton status event followed by Send SMS or Send SMS to List. The message can identify the project and status using mapped fields, while keeping the content plain text. This connection is set up through Zapier, so it is not a native two-way link between Baton and Mobile Message. Authorise both accounts, choose the event and action, test with a sample project, and enable the workflow when the recipients and timing are correct.