Record SMS replies
When a reply text arrives in Aircall, update the matching record in Stacker.
Google for Startups AcceleratorHow 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.
Stacker Explore Stacker →
TriggersFires when a new record is added to an app built in Stacker.
Fires when a record changes in an Stacker app.
Fires when a record is deleted in an Stacker app.
Adds a new record to an app built in Stacker.
Updates an existing record in an Stacker app.
Removes a record from an Stacker app.
Aircall Explore Aircall →
TriggersFires when a new text message is received in Aircall.
Fires when a new call comes in or out through Aircall.
Fires when a call is missed in Aircall.
Fires when a call recording finishes processing in Aircall.
Sends a text message through Aircall.
Starts an outbound call via Aircall.
Creates or updates a contact in Aircall.
Sends a recorded voice message via Aircall.
More Stacker + Aircall workflows
See all Stacker + Aircall integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Record SMS replies” between Stacker and Aircall?
Yes — describe it in the box above and Knit's Integrations Agent researches Stacker and Aircall'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.
Can a record send an SMS?
Yes. When a record is created or reaches a status in Stacker, Aircall can send a text to the customer or staff member.
Can calls be logged on records?
When a call or message is received in Aircall, the matching record in Stacker can be updated or created.