When new user in Brick FTP, sync it to Stripe (Legacy).

When a new user is created in Brick FTP, create customer records in Stripe (Legacy).

Try:

See all Brick FTP + Stripe (Legacy) 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.

Brick FTP Explore Brick FTP →

Triggers

New file uploaded

Fires when a new file is uploaded to Brick FTP.

File shared

Fires when a file in Brick FTP is shared with someone new.

Folder updated

Fires when a folder's contents change in Brick FTP.

Actions

Upload file

Uploads a file to Brick FTP.

Create folder

Creates a new folder in Brick FTP.

Share file

Shares a file from Brick FTP with a link or user.

Stripe (Legacy) Explore Stripe (Legacy) →

Triggers

New customer

Fires when a new customer is created in Stripe (Legacy).

Subscription canceled

Fires when a subscription is canceled in Stripe (Legacy).

New invoice generated

Fires when a new invoice is generated in Stripe (Legacy).

Payment failed

Fires when a payment attempt fails in Stripe (Legacy).

Actions

Create customer

Creates a new customer in Stripe (Legacy).

Create subscription

Creates a new subscription in Stripe (Legacy).

Cancel subscription

Cancels an existing subscription in Stripe (Legacy).

Update customer

Updates a customer's billing details in Stripe (Legacy).

Create dedicated storage folders for new subscribers When a new customer signs up in Stripe (Legacy), automatically create a personalized client folder in Brick FTP for storing invoices and assets. See details

Save generated subscription invoices to file storage Whenever a billing statement is created in Stripe (Legacy), convert and upload a copy of the invoice directly into a folder in Brick FTP. See details

Attach uploaded client documents to subscription accounts When a signed agreement or tax form is uploaded to Brick FTP, update the corresponding customer profile in Stripe (Legacy) to note the file location. See details

See all Brick FTP + Stripe (Legacy) integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “When new user in Brick FTP, sync it to Stripe (Legacy).” between Brick FTP and Stripe (Legacy)?

Yes — describe it in the box above and Knit's Integrations Agent researches Brick FTP and Stripe (Legacy)'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 invoices generated in Stripe (Legacy) be automatically saved to Brick FTP?

Yes, when a new invoice is created in Stripe (Legacy), a copy can be automatically saved to a designated folder in Brick FTP.

How does this integration assist with onboarding new subscribers?

Whenever a new subscriber registers in Stripe (Legacy), Brick FTP can automatically create a dedicated folder and share necessary account files with them.