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