Create new Glue threads for every new transaction in Mercury.
Whenever a new transaction takes place in Mercury, create a new thread in Glue.
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.
Glue Explore Glue →
TriggersFires when a new message is posted to a channel in Glue.
Fires when your team or a keyword is mentioned in Glue.
Fires when a new channel is created in Glue.
Fires when a new file is shared in Glue.
Posts a message to a channel in Glue.
Sends a direct message to a person in Glue.
Creates a new channel in Glue.
Adds a user to a channel in Glue.
Common questions
Can Knit build “Create new Glue threads for every new transaction in Mercury.” between Mercury and Glue?
Yes — describe it in the box above and Knit's Integrations Agent researches Mercury and Glue'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.