When incoming sms in Sendmode, sync it to TRIGGERcmd.
When an incoming SMS is received in Sendmode, trigger a command execution in TRIGGERcmd.
See all TRIGGERcmd + Sendmode 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.
TRIGGERcmd Explore TRIGGERcmd →
TriggersFires when a device connected to TRIGGERcmd comes online.
Fires when a device connected to TRIGGERcmd goes offline.
Fires when a reading from a device in TRIGGERcmd crosses a set threshold.
Sends a control command to a device via TRIGGERcmd.
Adds a new device to TRIGGERcmd.
Records a sensor reading or event from TRIGGERcmd.
Sendmode Explore Sendmode →
TriggersFires when a new text message is received in Sendmode.
Fires when a new call comes in or out through Sendmode.
Fires when a call is missed in Sendmode.
Fires when a call recording finishes processing in Sendmode.
Sends a text message through Sendmode.
Starts an outbound call via Sendmode.
Creates or updates a contact in Sendmode.
Sends a recorded voice message via Sendmode.
Common questions
Can Knit build “When incoming sms in Sendmode, sync it to TRIGGERcmd.” between TRIGGERcmd and Sendmode?
Yes — describe it in the box above and Knit's Integrations Agent researches TRIGGERcmd and Sendmode'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.