A campaign manager can be preparing a recipient record when an important Agillic event needs to reach someone quickly. A customer action may have configured effects in Agillic, but a separate SMS can make the next step more visible to a sales or service team. The recipient data and one-to-many tables stay in Agillic, while Mobile Message provides the text message.

With Zapier, Agillic's Get OTM Tables trigger can begin an action in Mobile Message. For example, a new table response can prompt a notification to a selected team list. You can also use Mobile Message's Inbound SMS Received trigger to run Agillic's Update or Create Recipient action, so a text from a customer can create or update a recipient record when the necessary fields are available.

This is a focused workflow rather than a general data sync. Agillic actions such as Create/Update a One-To-Many Record, Update or Create Recipient and Achieve Event remain available when Agillic is the action side of a Zap. Each workflow has one trigger and one action, and the message content or recipient fields depend on the data exposed by the chosen step.