Update customer details from internal docs
When a customer record is added or updated in Trainual, update the corresponding customer details in GoCardless to maintain accuracy.
See all Trainual + GoCardless 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.
Trainual Explore Trainual →
TriggersFires when a new page or doc is created in Trainual.
Fires when a new record is added to a database or table in Trainual.
Fires when a doc in Trainual is published or shared.
Fires when a status field changes on a record in Trainual.
Starts a new page in Trainual from a saved template.
Creates or updates a record in Trainual.
Adds text to the end of an existing doc in Trainual.
Moves a page in Trainual into a different space.
GoCardless Explore GoCardless →
TriggersFires when a new customer is created in GoCardless.
Fires when a subscription is canceled in GoCardless.
Fires when a new invoice is generated in GoCardless.
Fires when a payment attempt fails in GoCardless.
Creates a new customer in GoCardless.
Creates a new subscription in GoCardless.
Cancels an existing subscription in GoCardless.
Updates a customer's billing details in GoCardless.
More Trainual + GoCardless workflows
Create client workspace on new subscription
When a new customer subscribes in GoCardless, automatically create a dedicated client documentation page from a template in Trainual.
See details
Log payment failures in account docs
When a payment fails in GoCardless, add a record in Trainual so account managers can follow up immediately.
See details
See all Trainual + GoCardless integrations → · Browse the full workflow library →
Common questions
Can Knit build “Update customer details from internal docs” between Trainual and GoCardless?
Yes — describe it in the box above and Knit's Integrations Agent researches Trainual and GoCardless'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.
Why connect customer subscriptions to internal documentation?
It gives your customer success and delivery teams immediate visibility into subscriber statuses directly within the docs and databases they use daily in Trainual.
Can payment alerts be logged automatically in client documentation?
Yes, whenever a payment fails in GoCardless, a note or record can automatically be added to the customer's page in Trainual.