Flag cancellations
When a subscription is cancelled in Trolley, update the matching record in TITAN.
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.
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.
TITAN Explore TITAN →
TriggersFires when a new record is added to an app built in TITAN.
Fires when a record changes in an TITAN app.
Fires when a record is deleted in an TITAN app.
Adds a new record to an app built in TITAN.
Updates an existing record in an TITAN app.
Removes a record from an TITAN app.
More Trolley + TITAN workflows
See all Trolley + TITAN integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Flag cancellations” between Trolley and TITAN?
Yes — describe it in the box above and Knit's Integrations Agent researches Trolley and TITAN'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 new subscriptions create records?
Yes. When a subscription starts in Trolley, TITAN can create a record with the plan and customer.
Will cancellations show up?
When a subscription is cancelled or fails payment in Trolley, the record in TITAN can be updated so the team can act.