When payment status updated in Trolley, sync it to Lob.
When payment status updates in Trolley, trigger a check or mail confirmation via Lob.
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.
Trolley Explore Trolley →
TriggersFires when a new customer is created in Trolley.
Fires when a subscription is canceled in Trolley.
Fires when a new invoice is generated in Trolley.
Fires when a payment attempt fails in Trolley.
Creates a new customer in Trolley.
Creates a new subscription in Trolley.
Cancels an existing subscription in Trolley.
Updates a customer's billing details in Trolley.
Lob Explore Lob →
TriggersFires when a new print or mail job is submitted to Lob.
Fires when a print or mail job in Lob finishes or ships.
Sends a document or design to Lob to print.
Sends a physical postcard or letter via Lob.
Looks up the status of a print or mail job in Lob.
Common questions
Can Knit build “When payment status updated in Trolley, sync it to Lob.” between Trolley and Lob?
Yes — describe it in the box above and Knit's Integrations Agent researches Trolley and Lob'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.