A product team ships a fix, tweaks a price or adds a feature, then faces the unglamorous job of writing it up somewhere customers will actually see it. Without a habit of publishing updates, changes go unnoticed until a support ticket arrives asking why something is suddenly different, and by then the goodwill of announcing it first has already been lost.

ChangeCrab exists to make that part of the job less painful. Its Zapier action, Create Changelog, adds a new entry to a public changelog whenever an earlier step in a Zap decides one is needed, whether that's a completed deploy, an updated plan, a price change or a fix your team wants customers to know about. The entry goes up without anyone opening a separate app to write it from scratch.

Mobile Message connects to Zapier too, giving Create Changelog a natural neighbour in a wider workflow even though the two don't trigger each other directly. A business already texting customers through Mobile Message can let ChangeCrab handle the written record of what changed, while SMS carries the messages that need to land directly on a phone. Run side by side, the two cover both halves of telling customers something has changed, the public record and the personal message.