Revoke store permissions upon subscription cancellation

When a subscriber cancels their membership in Kobana (previously Boleto Simples), issue a custom API request to Magento 2.X to adjust their account level.

Try:

See all Kobana (previously Boleto Simples) + Magento 2.X integrations or talk to a human

Trusted by teams already building on Knit·

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.

Kobana (previously Boleto Simples) Explore Kobana (previously Boleto Simples) →

Triggers

New customer

Fires when a new customer is created in Kobana (previously Boleto Simples).

Subscription canceled

Fires when a subscription is canceled in Kobana (previously Boleto Simples).

New invoice generated

Fires when a new invoice is generated in Kobana (previously Boleto Simples).

Payment failed

Fires when a payment attempt fails in Kobana (previously Boleto Simples).

Actions

Create customer

Creates a new customer in Kobana (previously Boleto Simples).

Create subscription

Creates a new subscription in Kobana (previously Boleto Simples).

Cancel subscription

Cancels an existing subscription in Kobana (previously Boleto Simples).

Update customer

Updates a customer's billing details in Kobana (previously Boleto Simples).

Magento 2.X Explore Magento 2.X →

Triggers

New order

Fires when a customer places a new order in Magento 2.X.

Order status changed

Fires when an order in Magento 2.X is paid, fulfilled, refunded or disputed.

New customer

Fires when a new customer account is created in Magento 2.X.

Cart abandoned

Fires when a customer abandons their cart before completing checkout in Magento 2.X.

Actions

Create or update product

Creates or updates a product or listing in Magento 2.X.

Update order

Updates an order's status or fulfillment details in Magento 2.X.

Make a custom API request

Sends a custom API request to Magento 2.X for actions not covered by a dedicated action.

Sync recurring subscription buyers to your custom storefront When a new customer signs up in Kobana (previously Boleto Simples), make a custom API request in Magento 2.X to provision their store access instantly. See details

Update customer records when affiliate commission is earned When an affiliate earns a commission in Magento 2.X, automatically update the associated customer profile in Kobana (previously Boleto Simples) with updated reward balances. See details

See all Kobana (previously Boleto Simples) + Magento 2.X integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Revoke store permissions upon subscription cancellation” between Kobana (previously Boleto Simples) and Magento 2.X?

Yes — describe it in the box above and Knit's Integrations Agent researches Kobana (previously Boleto Simples) and Magento 2.X'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 customer accounts in Kobana (previously Boleto Simples) update storefront permissions in Magento 2.X?

Yes, when a customer subscribes in Kobana (previously Boleto Simples), you can issue a custom API request in Magento 2.X to grant specific storefront privileges.

How does this integration handle affiliate commissions for recurring payments?

When recurring invoices are generated or payments fail in Kobana (previously Boleto Simples), custom API requests can be sent to Magento 2.X to accurately adjust affiliate earnings.