When client cancels subscription in FITR, sync it to ClickSend SMS.
When a client cancels their subscription in FITR, send a notification SMS via ClickSend SMS.
See all FITR + ClickSend SMS integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
FITR Explore FITR →
TriggersFires when a new member, client or user joins in FITR.
Fires when someone books a class or session in FITR.
Fires when a workout, habit, journal entry or goal is logged in FITR.
Creates or updates a member's profile in FITR.
Books a class or session for a client in FITR.
Logs a workout, habit or data point in FITR.
ClickSend SMS Explore ClickSend SMS →
TriggersFires when a new text message is received in ClickSend SMS.
Fires when a new call comes in or out through ClickSend SMS.
Fires when a call is missed in ClickSend SMS.
Fires when a call recording finishes processing in ClickSend SMS.
Sends a text message through ClickSend SMS.
Starts an outbound call via ClickSend SMS.
Creates or updates a contact in ClickSend SMS.
Sends a recorded voice message via ClickSend SMS.
Common questions
Can Knit build “When client cancels subscription in FITR, sync it to ClickSend SMS.” between FITR and ClickSend SMS?
Yes — describe it in the box above and Knit's Integrations Agent researches FITR and ClickSend SMS's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.