Keep customer preference records up to date
When a subscriber unsubscribes in Dinamize, update their customer profile in Kobana (previously Boleto Simples) to align contact preferences across billing and marketing.
See all Kobana (previously Boleto Simples) + Dinamize integrations or talk to a human
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.
Kobana (previously Boleto Simples) Explore Kobana (previously Boleto Simples) →
TriggersFires when a new customer is created in Kobana (previously Boleto Simples).
Fires when a subscription is canceled in Kobana (previously Boleto Simples).
Fires when a new invoice is generated in Kobana (previously Boleto Simples).
Fires when a payment attempt fails in Kobana (previously Boleto Simples).
Creates a new customer in Kobana (previously Boleto Simples).
Creates a new subscription in Kobana (previously Boleto Simples).
Cancels an existing subscription in Kobana (previously Boleto Simples).
Updates a customer's billing details in Kobana (previously Boleto Simples).
Dinamize Explore Dinamize →
TriggersFires when a new subscriber is added in Dinamize.
Fires when a contact unsubscribes in Dinamize.
Fires when a subscriber opens or clicks a campaign in Dinamize.
Creates or updates a subscriber in Dinamize.
Unsubscribes a contact in Dinamize.
Adds a subscriber to a list or segment in Dinamize.
Sends a one-off transactional email via Dinamize.
More Kobana (previously Boleto Simples) + Dinamize workflows
See all Kobana (previously Boleto Simples) + Dinamize integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Keep customer preference records up to date” between Kobana (previously Boleto Simples) and Dinamize?
Yes — describe it in the box above and Knit's Integrations Agent researches Kobana (previously Boleto Simples) and Dinamize'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.
How does connecting Dinamize and Kobana (previously Boleto Simples) help reduce subscriber churn?
When payment failures or subscription cancellations happen in Kobana (previously Boleto Simples), automated workflows can immediately route customers into targeted re-engagement or recovery email sequences in Dinamize.
Can subscriber preference updates in Dinamize reflect in Kobana (previously Boleto Simples)?
Yes, when contacts unsubscribe or update preferences in Dinamize, workflows can automatically update their customer profile in Kobana (previously Boleto Simples) to maintain consistent communication preferences.