When cancelled transaction in Mercury, sync it to Twilio.
When a transaction is cancelled in Mercury, send an alert notification via Twilio.
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.
Mercury Explore Mercury →
TriggersFires when an employee submits a new expense in Mercury.
Fires when an expense in Mercury is approved.
Fires when an expense in Mercury is rejected.
Fires when a receipt is attached to an expense in Mercury.
Creates a new expense report in Mercury.
Approves a pending expense in Mercury.
Rejects a pending expense in Mercury.
Syncs an approved expense in Mercury to the general ledger.
Twilio Explore Twilio →
TriggersFires when a new text message is received in Twilio.
Fires when a new call comes in or out through Twilio.
Fires when a call is missed in Twilio.
Fires when a call recording finishes processing in Twilio.
Sends a text message through Twilio.
Starts an outbound call via Twilio.
Creates or updates a contact in Twilio.
Sends a recorded voice message via Twilio.
Common questions
Can Knit build “When cancelled transaction in Mercury, sync it to Twilio.” between Mercury and Twilio?
Yes — describe it in the box above and Knit's Integrations Agent researches Mercury and Twilio'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.