When cancelled transaction in Mercury, sync it to Google Forms.
When a transaction is cancelled in Mercury, log details in Google Forms response logs.
See all Mercury + Google Forms 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.
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.
Google Forms Explore Google Forms →
TriggersFires when a form is submitted in Google Forms.
Fires when a respondent finishes a survey in Google Forms.
Fires when an existing response is edited in Google Forms.
Creates or updates a form or survey in Google Forms.
Looks up a specific form response in Google Forms.
Adds a respondent or contact to a form in Google Forms.
Common questions
Can Knit build “When cancelled transaction in Mercury, sync it to Google Forms.” between Mercury and Google Forms?
Yes — describe it in the box above and Knit's Integrations Agent researches Mercury and Google Forms'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.